Last updated on MARCH 27, 2014
Applies to:Oracle Access Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Using OAM 18.104.22.168, in the Authorization Policy a header response was defined as following:
OAM_User_DN = $user.attr.dn
After accessing an OAM protected resource as user e.g. john.doe, when checking the returned header responses, you can see that OAM_User_DN has value "cn=john.doe:cn=users:dc=us:dc=oracle:dc=com".
While the expected value for this header response would be "cn=john.doe,cn=users,dc=us,dc=oracle,dc=com", as it happened in previous 11g releases of OAM.
In other words, in 22.214.171.124 release it appears that the usual RDNs separator "," was replaced with ":".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms