My Oracle Support Banner

EBS DIP Provisioning Profile Fails with OID 11g Error: [LDAP: error code 50 - Insufficient Access Rights]; remaining name '' (Doc ID 1507699.1)

Last updated on FEBRUARY 04, 2019

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.

Symptoms

EBS R12 integrated with OAM 11g and OID 11g.


Bi-directional EBS provisioning profiles "ApplicationToOID" and "OIDToApplication" repeatedly show these errors in wls_ods1_diagnostics.log:

[APP: DIP#11.1.1.2.0] Error occurs while initializing the provisioning profile.[[
javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient Access Rights]; remaining name ''
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3049)
(...)

 

Another symptom might be that changes within EBS are not propagated to OID and these errors are seen:

 

l_err_code :FND_SSO_UNEXP_ERROR, l_tmp_str :ORA-31202: DBMS_LDAP: LDAP client/server error: Insufficient access
ORA-31202: DBMS_LDAP: LDAP client/server error: Insufficient access

 In this case new users can be created without problems, and ACIs are default and have not changed, so Note 1311294.1 does not apply

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
References


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