DB EUS Logins Work with OID 11g Pre-18.104.22.168 But Fail with OID 22.214.171.124.0: ORA-28043: invalid bind credentials for DB-OID connection and/or ORA-28030: Server encountered problems accessing LDAP directory service. ldapbind Fails with: SSL handshake failed
(Doc ID 2098621.1)
Last updated on SEPTEMBER 18, 2019
Applies to:Oracle Internet Directory - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Existing Oracle Internet Directory (OID) 11g's, e.g., 188.8.131.52.0 and ealier, are working for Enterprise User Security (EUS) Database (DB) logins.
After installing a new OID 184.108.40.206.0 and migrating the EUS entries over from the older OID, EUS logins / global authentication configured to use the new 220.127.116.11 OID as LDAP server fail:
After correcting a password policy difference in the new 18.104.22.168 OID (for example, set the same value for pwdMaxAge to match the existing/working 22.214.171.124), EUS logins still fail with:
The data in both OID match exactly, including all the operational attribute values.
An OID debugged log reveals the same problem as outlined in the Symptoms of Document 1546173.1, where the EUS related search as orcladmin returns all the requested operational attributes, but the same search as the DB user returns only the dn and the orclguid from the nonworking OID, however that same Document Solution does not resolve the problem here.
Migrated EUS entries from older OID to new 126.96.36.199.0 OID.
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