AD Extended Attribute Is Not Updated During Provisioning And Existing Values Are Removed

(Doc ID 2404733.1)

Last updated on JUNE 03, 2018

Applies to:

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

Symptoms

After extending the AD Schema per Chapter 4 in the 11.1.1.6.0 AD UM Connector guide, if you attempt to provision a value to the newly added schema attribute the value is saved in OIM (i.e. in the UD_ADUSER table) but not on the AD target.

Furthermore, if a value already exists natively on the AD target for this newly added AD Schema attribute then that value is removed.

During a provision, if you run TRACE:32 on ORACLE.IAM.CONNECTORS, for the new schema attribute you will see something similar to the following in the OIM diagnostic log.  For example, if the extended AD Schema attribute form name is called "CustomAttr" you will see:

[SRC_CLASS: com.thortech.util.logging.Logger] [SRC_METHOD: debug] oracle.iam.connectors.icfcommon.prov.ProvEvent : handleField : Field [CustomAttr] mapped to [Attribute: {Name=CustomAttr, Value=[null]}]

Cause

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