LDAP Headers Not Set After Upgrading to 11.1.2.2.0 When Authenticating Through Custom Plugin
(Doc ID 1907648.1)
Last updated on OCTOBER 19, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.2.1 and laterInformation in this document applies to any platform.
Symptoms
After upgrading from 11.1.2.x to 11.1.2.2.0 authentication/authorization response headers set from LDAP attributes are no longer being set successfully (although authentication is successful). For example, a perl page that dumps headers shows results like:
* |HTTP_USER_NAME|
|uid=<VALUE>,ou=<VALUE>,dc=<VALUE>,dc=<VALUE>
* |HTTP_USER_ORCLGUID|
|$user.attr.orclguid|
* |HTTP_OAM_CN|
|$user.attr.CN|
When reviewing the OAM diagnostic log, we see errors similar to:
[2014-06-24T15:11:03.081-04:00] [oam_server1] [ERROR] [OAMSSA-20027] [oracle.oam.user.identity.provider] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1c71a126a927d027:-c39c394:146cbf343d0:-8000-00000000000076b5,0] [APP: oam_server#11.1.2.0.0] Could not get user : uid=<VALUE>,ou=<VALUE>,dc=<VALUE>,dc=<VALUE>, idstore: OVDStore, with exception: oracle.igf.ids.EntityNotFoundException: Entity not found for the search filter (&(objectclass=inetorgperson)(uid=<VALUE>,ou=<VALUE>,dc=<VALUE>,dc=<VALUE>))
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |