OUD to OIM Reconciliation Fails with "LDAP: error code 34" and "USER_NAME could not be parsed as a valid distinguished name .... unless the ds-cfg-allow-attribute-name-exceptions configuration option is enabled" (Doc ID 2811363.1)

Last updated on DECEMBER 30, 2022

Applies to:

Oracle Unified Directory - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

Unable to reconcile a specific user "WLS_IAM_USER" from OUD to OIM.

From OIM "SSO User Full Reconciliation" Scheduler job was run with filter" equalTo('cn','WLS_IAM_USER')" to reconcile user "WLS_IAM_USER" from OUD.

Recon is failing with the below errors.

javax.naming.InvalidNameException: WLS_IAM_USER: [LDAP: error code 34 - The provided value "WLS_IAM_USER" could not be parsed as a valid distinguished name because the underscore character is not allowed in an attribute name unless the ds-cfg-allow-attribute-name-exceptions configuration option is enabled]; remaining name 'WLS_IAM_USER'
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3198)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2996)

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

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.

OUD to OIM Reconciliation Fails with "LDAP: error code 34" and "USER_NAME could not be parsed as a valid distinguished name .... unless the ds-cfg-allow-attribute-name-exceptions configuration option is enabled" (Doc ID 2811363.1)

Applies to:

Symptoms

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!