Introduction
In Oracle APEX, the authentication scheme defines how users verify their identity when accessing an application. Sometimes you may need to change the authentication scheme—for example, switching from a development mode using APEX accounts to an enterprise LDAP setup. Changing the authentication scheme lets you adapt your application’s security as requirements evolve while maintaining control over user access.
How to Change the Authentication Scheme Associated with an Application in Oracle APEX
-
Open Your Application
Log in to Oracle APEX and open the application where you want to change the authentication scheme. -
Navigate to Authentication Schemes
From the application home page, go to Shared Components and click Authentication Schemes under the Security section. -
View Available Schemes
You will see a list of all authentication schemes defined for the application. One of them will be marked as (Current), indicating the active scheme. -
Select the Desired Scheme
Identify the authentication scheme you want to activate. This might be a preconfigured scheme such as LDAP, Social Sign-In, or a custom scheme you created earlier. -
Make the Scheme Current
Click the name of the desired authentication scheme to open its details. Then click the Make Current button to activate it for the application. -
Test the New Authentication Scheme
Run your application and verify the login process to ensure the new scheme works as expected for your users.
Best Practices
-
Backup your application or document existing settings before changing the scheme.
-
Test new authentication schemes in a development or staging environment before applying to production.
-
Inform your users about any changes to the login process.
-
Use clear naming conventions for your authentication schemes to avoid confusion.
-
Combine authentication scheme changes with appropriate authorization schemes for fine-grained access control.
Oracle APEX allows you to change the authentication scheme of an application to switch between different authentication methods. This is useful when updating security policies, integrating with external identity providers, or testing different authentication approaches.
Steps to Change the Authentication Scheme
Navigate to the Authentication Schemes Page
Log in to your Oracle APEX workspace.
Open App Builder and select the application you want to modify.
Click Shared Components from the application menu.
Under Security, select Authentication Schemes.
Select a Different Authentication Scheme
The Authentication Schemes page displays all available authentication schemes for the application.
Locate the authentication scheme you want to set as the new default.
Click on the scheme name to open its Edit Authentication Scheme page.
Make the Authentication Scheme Current
Click the Make Current button to activate the selected authentication scheme for the application.
This will replace the previously active authentication scheme.
Verify Authentication Settings
Ensure that the newly selected authentication scheme is configured correctly.
If using a custom authentication scheme, verify the PL/SQL function for user validation.
If integrating with external providers (e.g., LDAP, SAML, Social Sign-In), ensure the necessary credentials and API settings are correctly configured.
Test the New Authentication Scheme
Run the application and attempt to log in with valid credentials to confirm authentication is working as expected.
If issues arise, review the authentication scheme settings or check error logs for troubleshooting.
By changing the authentication scheme in Oracle APEX, you can adapt your application to new authentication methods, enhance security, or integrate with enterprise identity providers.
Oracle APEX Documentation
For detailed instructions and additional options, see the official documentation:
https://docs.oracle.com/en/database/oracle/apex/23.2/aeapp/changing-authentication-schemes.html
Conclusion
Changing the authentication scheme in Oracle APEX is a straightforward way to update how users access your application as your security needs evolve. By following the proper steps and best practices, you can switch schemes confidently without disrupting user experience, ensuring your application remains secure and easy to use.
