cancel
Showing results for 
Search instead for 
Did you mean: 

CUP - Error in LDAP Authentication

Former Member
0 Kudos

Hello Experts ,

We have implmented CUP & have congigured LDAP as authentication mechanism.

The LDAP connector works fine but when I try to logon with my login credentials it gives an erroe. The error log is as follows;

I have configured LDAP mapping. However , I have my doubts about the configuration done in Connectore especially fileds , Domain & User Path.

Can somebody let me know the correct way to enter these filed values.

2009-04-14 18:47:19,814 [SAPEngine_Application_Thread[impl:3]_29] ERROR Failed to log in shailesh.a.deshpande

com.virsa.ae.service.umi.AuthenticationFailureException: No user details found

at com.virsa.ae.service.umi.ldap.LDAPAuthenticator.authenticate(LDAPAuthenticator.java:302)

at com.virsa.ae.actions.LoginAction.requestorLoginHandler(LoginAction.java:1116)

at com.virsa.ae.actions.LoginAction.execute(LoginAction.java:93)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: com.virsa.ae.core.ObjectNotFoundException: No valid user found for account name: shailesh.deshpande at com.virsa.ae.service.umi.ldap.LDAPSearchUser.getUserById(LDAPSearchUser.java:848)

at com.virsa.ae.service.umi.ldap.LDAPAuthenticator.authenticate(LDAPAuthenticator.java:295)

... 19 more

Can you help me with how to proceed ..

Regards,

Shailesh

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Shailesh,

Most likely the CUP is not able to log-in to the LDAP Domain properly. You just need to enter complete Domain path as well as User Principle Name.

eg. for Active Directory you can fill the details as follows

Domain as DC=devserver,DC=dev,DC=client,DC=corp for devserver.dev.client.corp

and User Principle Name as shailesh@Domain (devserver.dev.client.corp)

I hope this will do the needful.

--

Cheers,

Aman

GRC RIG

Former Member
0 Kudos

Thanks for your suggestions guys.

The issue is solved now. It was the issue with incorrect domain name provided in the connectore.

Regards,

Shailesh

Former Member
0 Kudos

If the connector is working from the "test connection" page then it shouldn't be a connection issue.

- To verify I would leave the User Path and Group Path blank, that will ensure it is pulling from the top of the directory tree.

- Also make sure the field mapping is correct for the User ID most likley it will be mapped to "sAMAccountName"

- When attempting to connect through CUP make sure that you do not include the domain just the user ID.

Hope this helps.

Former Member
0 Kudos

Shailesh,

Christopher is right. There can not be a connection issue here. Follow his recommendations and check this document:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b089fb71-a3b7-2a10-64a2-8c77243b...

Regards,

Alpesh