LDAP Authentication Not Working After Upgrade From Oracle Secure Global Desktop (SGD) 5.5 To 5.6
(Doc ID 2753267.1)
Last updated on JUNE 15, 2023
Applies to:
Oracle Secure Global Desktop - Version 5.6 and laterInformation in this document applies to any platform.
Symptoms
LDAP Authentication was working on 5.5 but not working after upgrade from 5.5 to 5.6.
Errors such as this below can be seen in the logs.
----
The login authority com.sco.tta.server.login.ldap.LdapLoginAuthority encountered an error.
Exception was: com.sun.directoryservices.service.NameNotFoundException: No such object, null [Root exception is com.sun.directoryservices.service.NameNotFoundException: No such object, null [local: No such object, null, response: DirectoryResponse(code=32,message='No such object')]] [local: No such object, null, response: DirectoryResponse(code=32,message='No such object')]
at com.sun.sgd.directoryservices.core.auth.managers.StandardLDAPUserManager.findCandidates(StandardLDAPUserManager.java:99)
----
The user is using his sAMAccountName to login.
Changes
A defect introduced in SGD version 5.6 and remedied in Update 1 to SGD 5.6.
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 |