How to Update All DIP Synchronized Entries in OID After Changing Profile Domain or Attribute Mappings? How to Trigger a DIP Sync After Mapping Rules Are Changed?
(Doc ID 460596.1)
Last updated on AUGUST 30, 2023
Applies to:
Oracle Internet Directory - Version 9.0.4 and laterInformation in this document applies to any platform.
Goal
Q1: DIP synchronization from OID to Active Directory (AD) has been configured successfully, but there is a requirement to change the mapping of certain OID attribute values.
For example, the field "Known as" in OIDDAS User Profile is displayed with only the user's first name. It may be a business requirement to display the person's complete name.
The 'Known As' OIDDAS value corresponds with the displayName attribute in OID.
When users are synchronized from AD to OID the OID displayName attribute is usually mapped from AD attribute givenName, i.e.,
How to change this mapping?
Q2: After changing the DIP sync profile Active Directory -> OID attribute mapping rules, how to trigger a sync to update all users in OID with the new mappings?
Solution
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
Goal |
Solution |
References |