My Oracle Support Banner

OAM - $user.attr.dn Returns A DN With : Used As The RDN Seperator (Doc ID 1631205.1)

Last updated on MAY 24, 2022

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


Using OAM, 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 <uername>, when checking the returned header responses, you can see that OAM_User_DN has value "cn=<username>:cn=users:dc=us:dc=<company>:dc=com".
While the expected value for this header response would be "cn=<username>,cn=users,dc=us,dc=<company>,dc=com", as it happened in previous 11g releases of OAM.

In other words, in release it appears that the usual RDNs separator "," was replaced with ":".




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.