DIP Synchronization For AD ObjectGUID to OID Custom Attribute, DIP is Storing it Incorrectly in OID, with Wrong Format, Not in Same Binary Value
(Doc ID 2407068.1)
Last updated on NOVEMBER 08, 2019
Applies to:Oracle Internet Directory - Version 9.0.4 and later
Information in this document applies to any platform.
Using Directory Integration Platform (DIP) to synchronize from Microsoft (MS) Active Directory (AD) ObjectGUID to Oracle Internet Directory (OID) custom attribute, e.g., <CUSTOM_ATTRIBUTE>
The custom attribute format/value needs to match the AD ObjectGUID format/value exactly in order to work with third party application. The application works directly against AD using the objectGUID.
The schema definition for the custom attribute in OID matches the objectGuid in AD, e.g.:
Tried specifying an attribute mapping expression to convert the value to base64, it seems to be stored correctly but the application expects the value to be stored in binary, so it still fails.
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