Original Login Exception from LDAP is not Propagated After Setting the wlp.propogate.login.exception.cause Flag to True
(Doc ID 860345.1)
Last updated on JANUARY 21, 2025
Applies to:
Oracle WebLogic Portal - Version 9.2.0 to 10.3.7 [Release Weblogic Platform to AS10gR3]Information in this document applies to any platform.
Symptoms
Weblogic Portal's Authentication.login() API only provides generic error messages if LDAP authentication fails. The exact LDAP error code is not retrieved and it does not tell why the authentication has failed.
When starting the WebLogic server with the wlp.propagate.login.exception option enabled (set to true), the following exception is thrown:
So even when the wlp.propagate.login.exception flag is enabled, the exact error code from the underlying LDAP is not retrievable.
Also, WebLogic does not distinguish the failed login for any of the following reasons:
- The user has not provided valid credentials
- The user is not present in the LDAP store
- The user's account is disabled in the LDAP store
Cause
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
| Symptoms |
| Cause |
| Solution |