Oracle Access Manager (OAM) Federation - Process Is Not Working As LDAP Attributes Are Not Being Populated As Expected In The SAML Assertion
(Doc ID 2833732.1)
Last updated on APRIL 21, 2023
Applies to:
Oracle Access Manager - Version 12.2.1.3.210324 and laterInformation in this document applies to any platform.
Symptoms
OAM SAML Federation not working as LDAP attributes are not being populated in the SAML assertion.
- OAM is the Identity Provider (IdP).
- Service Provider (SP) Attribute Mapping Profile defined with multiple user profile attributes to be fetched from OUD following a successful authentication and include n SAMLResponse to be sent to SP.
- Following a successful authentication, the SAML Response contains all the configured attributes except 2: displayName and givenName.
- Review of the OAM Diagnostic Log suggests that OAM fetches the attributes from OUD, as expected.
Why are the 2 specific attributes are empty (No values) in the SAMLResponse?
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 |