Reputation: 11
What is the difference between built-in authentication and custom authentication in oracle apex 5?
What are the limitation in using built-in authentication in apex 5?
What are the cons and pros built-in authentication and custom authentication?
Upvotes: 1
Views: 1473
Reputation: 4874
Built-in as in Apex authentication?
Since I am a senior Oracle programmer, I tend to always use Custom and program the authentication myself.
Apex has the following authentication schemes:
1) Application Express Accounts
** Pros - Easy to use (full interface with apex)
** Cons - Can't limit users between applications (within a workspace)
2) Database Accounts
** Pros - If you have an application that uses oracle schema for authentication, then this provides easy integration
** Cons - Database accounts
3) Custom (most common)
** Pros - Great if you are accessing a system with different front-ends or if you are extending a system that already has it's authentication scheme set-up. IF you can code it in pl/sql or Java, you can authenticate.
** Cons - You need to code the whole user admin interface (if needed)
4) HTTP Header Variable
** Pros - Integrates easily if your network has a SSO server that sets a header variable by the web server
** Cons - Haven't found many use cases for this
5) LDAP Directory
** Pros - Great to simply use your companies LDAP for authentication
** Cons - I have found that it's more flexible to simply use custom authentication and dbms_ldap
for Microsoft Active Directory.
6) Open Door Credentials
** No pros or cons. This is simply for testing. System asks you for a username and uses that username henceforth. (no password or checks)
7) Oracle Application Server Single Sign-On
** Pros - If your company uses Oracle's SSO server (E-business suite for example) then this is for you.
** Cons - You need Oracle's SSO server :)
8) No Authentication (Using DAD)
** Pros - No login - Open website
** Cons - No login - Open website
Upvotes: 7