AD to OID 10.1.4.2 Or 10.1.4.3 Bootstrapped Users Fail To Login To SSO Applications / ssoServer.log Shows Errors: General Error when performing search<entryDN> / Invalid name

(Doc ID 1357455.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Application Server Single Sign-On - Version 10.1.4.2 to 10.1.4.3 [Release 10gR3]
Oracle Internet Directory - Version 10.1.4.2 to 10.1.4.3 [Release 10gR3]
Information in this document applies to any platform.

Symptoms

Oracle Internet Directory (OID) Directory Integration Platform (DIP) 10g 10.1.4.2 or 10.1.4.3.

Some AD to OID bootstrapped users are unable to login to Single Sign-On (SSO) applications.

The ssoServer.log shows:

Wed Aug 31 08:31:31 EDT 2011 [ERROR] AJPRequestHandler-ApplicationServerThread-12 Could not get attributes for user, FirstInitialLastName
oracle.ldap.util.UtilException: General Error when performing searchcn=LastName, FirstName I.,cn=Users,dc=mycompany,dc=com Invalid name: cn=LastName, FirstName I.,cn=Users,dc=mycompany,dc=com
at oracle.ldap.util.PropertySet.doSearch(PropertySet.java:304)
at oracle.ldap.util.LDAPEntry.getProperties(LDAPEntry.java:129)
at oracle.ldap.util.User.getProperties(User.java:830)
at oracle.security.sso.server.ldap.OIDUserRepository.getUserProperties(OIDUserRepository.java:547)
at oracle.security.sso.server.auth.SSOServerAuth.authenticate(SSOServerAuth.java:508)
at oracle.security.sso.server.ui.SSOLoginServlet.processSSOPartnerRequest(SSOLoginServlet.java:1076)
at oracle.security.sso.server.ui.SSOLoginServlet.doPost(SSOLoginServlet.java:547)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:826)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:332)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)



In looking for differences between working and non-working entries, using either ldapsearch command line:

ldapsearch -h <oid host> -p <port> -D cn=orcladmin -w <password> -b "cn=users,dc=mycompany,dc=com" -s sub "(cn=*LastName*)"


Or viewing the user entry in OID in Oracle Directory Manager (ODM / oidadmin), the non-working entries display with the RDN value of the DN (CN in this case) enclosed in doublequotes, e.g.:

cn="LastName, FirstName I.",cn=users,dc=mycompany,dc=com
orclsourceobjectdn=CN=LastName\, FirstName I.,OU=Users,DC=mycompany,DC=com
cn=LastName, FirstName I.
..<etc>...


Also, clicking on this user entry in ODM/oidadmin fails with:  Error 0 (zero).

And these entries will also show enclosed in doublequotes in the resulting bootstrap.log from a bootstrap attempt.

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms