OVD 11g 220.127.116.11 Does Not Map AD ObjectGUID in Correct Format (Base64 / Hexadecimal)
Last updated on NOVEMBER 23, 2017
Applies to:Oracle Virtual Directory - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Oracle Virtual Directory (OVD) 11g 22.214.171.124.0.
An application needs the orclguid value (which is mapped to the backend objectguid value through the default objectclass mapper plug-in) to be in the original Microsoft (MS) Active Directory (AD) hexadecimal format.
However, OVD is not returning this value in hex format so the application sees an invalid format, such as directory string format.
For example, directly to AD:
Further, taking the value of orclGUID and convert it back to base 64: 3518db8aabe64889844efdb1b3b6e086
To base64 encoded, a different value is returned: NRjbiqvmSImETv2xs7bghg==
Whereas the original Base64 value for objectGUID from AD is: itsYNeariUiETv2xs7bghg==
Tried to implement:
Document 1475299.1 How To Map objectguid attribute from AD in OVD
However it did not work.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms