21.4.2 Understanding Preconfigured Authentication Schemes

Learn about the preconfigured authentication schemes.

When you create an authentication scheme from the gallery, you can select a preconfigured authentication scheme which follows a standard behavior for authentication and session management. To associate an authentication scheme with an application, you select the application and create a new authentication scheme. A newly created authentication scheme is not enabled by default. To enable the new authentication scheme for an application, edit the authentication scheme and click Make Current Scheme.

This section describes all preconfigured authentication schemes that ship with Oracle APEX.

Tip:

Authentication schemes support plug-ins. To learn more, see Implementing Plug-ins.

• Oracle APEX Accounts
  Oracle APEX Accounts are user accounts that are created within and managed in the APEX user repository. When you use this method, your application is authenticated against these accounts.
• Custom Authentication
  Creating a Custom Authentication scheme from scratch to have complete control over your authentication interface.
• Database Accounts
  Database Account Credentials authentication utilizes database schema accounts to authenticate users.
• HTTP Header Variable
  Authenticate users externally by storing the username in a HTTP Header variable set by the web server.
• Open Door Credentials
  Enable anyone to access your application using a built-in login page that captures a user name.
• No Authentication (using DAD)
  Adopts the current database user. This approach can be used in combination with a mod_plsql Database Access Descriptor (DAD) configuration that uses basic authentication to set the database session user.
• LDAP Directory
  Authenticate a user and password with an authentication request to a LDAP server.
• Oracle Application Server Single Sign-On Server
  Delegates authentication to the Oracle AS Single Sign-On (SSO) Server. To use this authentication scheme, your site must have been registered as a partner application with the SSO server.
• SAML Sign-In
  Delegates authentication to the Security Assertion Markup Language (SAML) Sign In authentication scheme.
• Social Sign-In
  Social Sign-In supports authentication with Google, Facebook, and other social networks and enterprise identity providers that support OpenID Connect or OAuth2 standards.

See Also:

• Changing the Authentication Scheme Associated with an Application
• Configuring Authentication Schemes for an Instance in Oracle APEX Administration Guide

21.4.2.1 Open Door Credentials

Enable anyone to access your application using a built-in login page that captures a user name.

Open Door Credentials enables anyone to access your application using a login page that captures a user name. This authentication scheme is useful during application development.

• Setting Up Open Door Credentials
  Learn how to set up Open Door Credentials authentication.

21.4.2.1.1 Setting Up Open Door Credentials

Learn how to set up Open Door Credentials authentication.

To set up Open Door Credentials authentication:

1. On the Workspace home page, click the App Builder icon.
2. Select an application.
3. On the Application home page, click Shared Components.

   The Shared Components page appears.

4. Under Security, select Authentication Schemes.
5. On the Authentication Schemes page, click Create.
6. Select Based on a pre-configured scheme from the gallery and click Next.
7. Under Name:
   1. Name - Enter the name used to reference the authentication scheme by other application developers.
   2. Scheme Type - Select Open Door Credentials.
8. Click Create Authentication Scheme.