It's all about the answers!

Ask a question

CLM5.0.2 Change LDAP OU configuration


Nada Loutfallah (1614) | asked Jul 18 '16, 3:09 a.m.
edited Jul 18 '16, 3:11 a.m. by Ralph Schoon (63.4k33646)
 Hi,

I cannot access my CLM application I have a problem in the LDAP OU configuration a connection refused appear in the log so I need to change manually the configuration what files must be changed.
Changing the following 2 files (server.xml and teamserver.properties) doesn't solve the problem.
system Info:
CLM 5.0.2 fix 12
Apache Tomcat
SQL server 2012
Windows 2008

Thanks

Comments
Lily Wang commented Jul 18 '16, 4:05 a.m.

The files you changed are correct. Could you provide the detail errors in the log? It would be good if you can also provide the LDAP related configuration in server.xml and jts/teamserver.properties.

2 answers



permanent link
Nada Loutfallah (1614) | answered Jul 18 '16, 4:59 a.m.
 Hi Lily,

Kindly check the catalina log:

INFO: Exception performing authentication. Retrying...
Throwable occurred: javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 ]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3079)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3025)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2827)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2741)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:308)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:187)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:205)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:148)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:78)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:250)
at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
at javax.naming.InitialContext.internalInit(InitialContext.java:286)
at javax.naming.InitialContext.<init>(InitialContext.java:211)
at org.apache.catalina.realm.JNDIRealm.open(JNDIRealm.java:2098)
at org.apache.catalina.realm.JNDIRealm.startInternal(JNDIRealm.java:2189)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1109)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:300)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:731)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.startup.Catalina.start(Catalina.java:689)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:321)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Jul 18, 2016 9:44:22 AM org.apache.catalina.startup.Catalina start
SEVERE: The required Server component failed to start so Tomcat is unable to start.
Throwable occurred: org.apache.catalina.LifecycleException: Failed to start component [StandardServer[9005]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.startup.Catalina.start(Catalina.java:689)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:321)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardService[Catalina]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:731)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 9 more
Caused by: org.apache.catalina.LifecycleException: Failed to start component [Realm[JNDIRealm]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1109)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:300)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 11 more
Caused by: org.apache.catalina.LifecycleException: Exception opening directory server connection
at org.apache.catalina.realm.JNDIRealm.startInternal(JNDIRealm.java:2191)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 14 more
Caused by: javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]
at com.sun.jndi.ldap.Connection.<init>(Connection.java:213)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:128)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1601)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2690)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:308)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:65)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:250)
at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
at javax.naming.InitialContext.internalInit(InitialContext.java:286)
at javax.naming.InitialContext.<init>(InitialContext.java:211)
at org.apache.catalina.realm.JNDIRealm.open(JNDIRealm.java:2108)
at org.apache.catalina.realm.JNDIRealm.startInternal(JNDIRealm.java:2189)
... 15 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:412)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:271)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:258)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:376)
at java.net.Socket.connect(Socket.java:546)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.sun.jndi.ldap.Connection.createSocket(Connection.java:352)
at com.sun.jndi.ldap.Connection.<init>(Connection.java:200)
... 27 more
Jul 18, 2016 9:44:22 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-9080"]
Jul 18, 2016 9:44:22 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-9443"]
Jul 18, 2016 9:44:22 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-9009"]
Jul 18, 2016 9:44:22 AM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
Jul 18, 2016 9:44:22 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-9080"]
Jul 18, 2016 9:44:22 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-9443"]
Jul 18, 2016 9:44:22 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-bio-9009"]

Comments
Lily Wang commented Jul 18 '16, 5:53 a.m.

"data 52e" means invalid credential. If you have confirmed the issue was happened after changed OU and the LDAP username and password are correct, you can use  LDAP Browser to check if the current OU setting is correct.


permanent link
Nada Loutfallah (1614) | answered Jul 18 '16, 7:55 a.m.
 Hi Lily,

the username and password are correct also we are able to connect using the same user on Softerra LDAP browser and to check the OU configuration. the problem start before changing the OU.
What can be the problem??

Thanks

Comments
Lily Wang commented Jul 18 '16, 8:23 p.m.

I can not provide further suggestion on your issue as I don't know how you set the OU in LDAP server. As the error is related to "Invalid Credential", please ensure the bind user is not locked and the password is correct.
Please also check https://tomcat.apache.org/tomcat-7.0-doc/realm-howto.html#JNDIRealm to ensure the LDAP setting in server.xml is correct.


Nada Loutfallah commented Jul 19 '16, 1:11 a.m.

  Thanks Lily,


The problem has been solved by replacing the user name by it fully qualified name 

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.