My Oracle Support Banner

Modifying Decode Value of 'Name' Attribute in the Lookup 'Lookup.OID.UM.ProvAttrMap' Does not Reflect the Change (Doc ID 2616745.1)

Last updated on DECEMBER 10, 2019

Applies to:

Identity Manager Connector - Version 11.1.1.5.0 and later
Identity Manager - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

In an OIG 12c environment, when a compatible OID Connector is deployed using Application onboarding and when the 'Name' (Code) Attribute's Value is modified in the 'Lookup.OID.UM.ProvAttrMap' with respect to OID Connector from the default value (Meaning/Decode) __NAME__="uid=${User_ID},${Container_DN}" to any other value as desired, for example: __NAME__="cn=${Common_Name},${Container_DN}" the below error can observed while 'CREATEUSER' task runs.

From the above errors, It can be observed that the 'CREATEUSER' task is still using the Attribute: {Name=__NAME__, Value=[uid=<uid>,<ContainerDN>]} even though the the lookup 'Lookup.OID.UM.ProvAttrMap' is modified to use the desired value.

The actual Attribute should have been {Name=__NAME__, Value=[cn=<Common_Name>,<ContainerDN>]}, but this is not reflected and thus, CREATEUSER task is not successful.

Changes

The 'Name' (Code) Attribute's Value is modified in the 'Lookup.OID.UM.ProvAttrMap' with respect to OID Connector from the default value (Meaning/Decode) __NAME__="uid=${User_ID},${Container_DN}" to any other value as desired, for example, __NAME__="cn=${Common_Name},${Container_DN}"

Cause

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
Symptoms
Changes
Cause
Solution


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