Identity Management (MOSC)

MOSC Banner

Unable to bind to the OID via ldapbind

edited Feb 18, 2015 10:00AM in Identity Management (MOSC) 5 commentsAnswered
Hi Gurus,

I have  IDM11g (OID 11.1.1.1.5) which is synced to  AD via DIP.   In the DIP  mapping,   UserPrincipalName(UPN) of AD is mapped to different attributes and same UPN is also mapped to "mail" attribute of inetOrgperson object.  This is required custom mapping to ensure the "Email Address" in OID  has the corporate email.  Everything works fine, but somehow when the UPN is updated, and changed to back to "Original UPN"  the  link for tht user account is broken and unable to bind the user  via "ldapbind"

Since this is also linked to EBS, we can't delete the user in OID / AD because it will have impact with EBS.  How to clean such kind of issues.  Resetting the password does not work.   Interestingly the AD authentication works for Desktop Login and Desktop Application.  What is that different in OID which makes the "ldapbind" failing.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center