Custom Authentication code (LDAP) gives "Invalid Credentials" Only for One Workspace
(Doc ID 1933426.1)
Last updated on FEBRUARY 18, 2021
Applies to:Oracle Application Express (APEX) - Version 4.2.5.00 and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Using: APEX 4.2.5 installed in 2 different environments (Development and Production)
To be able to authenticate using the same application/credentials in all environments using custom authentication code. The same code works as expected in one environment for all workspaces, and in some workspaces in the affected environment.
When using custom code to authenticate via LDAP an "invalid credentials" error is raised in one environment (Prod) for but not other (Dev), even though the same credentials are used in both, and both environments are configured to use the same LDAP resource. Additionally, it should be noted that the problem does not occur in all Prod workspaces/applications, where the Workspace Parsing Schema is different from that used by the affected Workspace/Applications.
STEPS TO REPRODUCE (assumes customer test case)
The issue can be reproduced at will with the following steps:
- Import the application with custom authentication code and related objects into a new environment (Prod)
- Test the authentication login, and receive "invalid credentials" message
- Import the same application into a different Workspace also in the Prod environment
- Test the authentication login using the same credentials and authentication is successful
Apex was upgraded from 4.1 to 4.2.5 recently in all environments
Moving the application from one environment where it works (Dev) to another (Prod) using apex export/import. where nothing is changed in the application or the custom authentication code
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document