My Oracle Support Banner

Third Party Ldap Security Provider Association Does Not Work In 10.1.3.5 (Doc ID 1285640.1)

Last updated on OCTOBER 11, 2019

Applies to:

Oracle Containers for J2EE - Version 10.1.3.5.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.

Symptoms


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.

ERROR
------------

2011-01-12 05:11:31.453 TRACE LDAP server: ldap://<HOSTNAME>:<PORT>; LDAP user: <ADMIN_USER>@<COMPANY>.com; useConnectPool: true
2011-01-12 05:11:31.546 TRACE search filter: (&(objectclass=inetOrgPerson)(sAMAccountName=<USER>))
2011-01-12 05:11:31.546 TRACE search base: cn=users,dc=<COMPANY>,dc=com
2011-01-12 05:11:31.562 TRACE JAAS-LDAPLoginModule: DN for user <USER> is null
2011-01-12 05:11:31.562 NOTIFICATION JAAS-LDAPLoginModule: User with name <USER> does not exist.
2011-01-12 05:11:31.562 ERROR JAAS-LDAPLoginModule: Authentication failed: unable to find user <USER>
2011-01-12 05:11:31.562 TRACE JAAS-LDAPLoginModule: Authentication failed: unable to find user <USER>

Changes

 

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
Changes
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.