Third Party Ldap Security Provider Association Does Not Work In 10.1.3.5
Last updated on OCTOBER 20, 2017
Applies to:Oracle Containers for J2EE - Version: 10.1.3.5.0 to 10.1.3.5.0 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
Authentication via third party ldap to deployed applications in AS10.1.3.1- AS10.1.3.3 works fine. However upon upgrade to AS 10.1.3.5 an error occurs although the same set up procedure and same user account in the ldap provider were being applied.
2011-01-12 05:11:31.453 TRACE LDAP server: ldap://xxxxxx.us.oracle.com:389; LDAP user: Administrator@ad.vm.oracle.com; useConnectPool: true
2011-01-12 05:11:31.546 TRACE search filter: (&(objectclass=inetOrgPerson)(sAMAccountName=oracle))
2011-01-12 05:11:31.546 TRACE search base: cn=users,dc=ad,dc=vm,dc=oracle,dc=com
2011-01-12 05:11:31.562 TRACE JAAS-LDAPLoginModule: DN for user oracle is null
2011-01-12 05:11:31.562 NOTIFICATION JAAS-LDAPLoginModule: User with name oracle does not exist.
2011-01-12 05:11:31.562 ERROR JAAS-LDAPLoginModule: Authentication failed: unable to find user oracle
2011-01-12 05:11:31.562 TRACE JAAS-LDAPLoginModule: Authentication failed: unable to find user oracle
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms