JIRA use Crowd Login Invalid

Jiannan Tang January 9, 2013

Hi:

I create a direction use Delegated Authentication Directory.

But sometime login error, is somethin wrong with LDAP Server.

Other Systems login use the same LDAP server are successful.

JIRA log:

login : 'tangjn1' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie

Crowd Log:

2013-01-10 21:55:08,684 http-8095-4 ERROR [crowd.manager.application.ApplicationServiceGeneric] Directory 'JIRA_LDAP' is not functional during authentication of 'tangjn'. Skipped.

2013-01-10 21:55:08,687 http-8095-4 ERROR [console.action.application.ViewApplication] org.springframework.ldap.CommunicationException: 10.125.3.6:389; nested exception is javax.naming.CommunicationException: 10.125.3.6:389 [Root exception is java.net.ConnectException: Connection timed out]

com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.CommunicationException: 10.125.3.6:389; nested exception is javax.naming.CommunicationException: 10.125.3.6:389 [Root exception is java.net.ConnectException: Connection timed out]

at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:407)

at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntities(SpringLDAPConnector.java:375)

at com.atlassian.crowd.directory.SpringLDAPConnector.searchUserObjects(SpringLDAPConnector.java:565)

at com.atlassian.crowd.directory.SpringLDAPConnector.findUserWithAttributesByName(SpringLDAPConnector.java:531)

at com.atlassian.crowd.directory.SpringLDAPConnector.findUserByName(SpringLDAPConnector.java:518)

at com.atlassian.crowd.directory.SpringLDAPConnector.authenticate(SpringLDAPConnector.java:952)

at com.atlassian.crowd.directory.DelegatedAuthenticationDirectory.authenticate(DelegatedAuthenticationDirectory.java:167)

at com.atlassian.crowd.manager.directory.DirectoryManagerGeneric.authenticateUser(DirectoryManagerGeneric.java:279)

at sun.reflect.GeneratedMethodAccessor364.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)

at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)

at com.atlassian.spring.interceptors.SpringProfilingInterceptor.invoke(SpringProfilingInterceptor.java:16)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)

at $Proxy10.authenticateUser(Unknown Source)

at com.atlassian.crowd.manager.application.ApplicationServiceGeneric.authenticateUser(ApplicationServiceGeneric.java:121)

at sun.reflect.GeneratedMethodAccessor349.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)

at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)

at com.atlassian.spring.interceptors.SpringProfilingInterceptor.invoke(SpringProfilingInterceptor.java:16)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)

at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)

at $Proxy11.authenticateUser(Unknown Source)

at com.atlassian.crowd.manager.application.CachingApplicationService.authenticateUser(CachingApplicationService.java:60)

at sun.reflect.GeneratedMethodAccessor349.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

4 answers

1 accepted

0 votes
Answer accepted
Septa Cahyadiputra
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 9, 2013

Hi Jiannan,

Judging from the provided stack trace, it seems that the cause of the issue is due to connection timed out when Crowd is trying to connect to your LDAP server to authenticate the user. In order to troubleshoot this issue, you could start by increasing the timed out configuration on Crowd directory side and see if the condition improve.

If it is not improve, you might want to check if there are any DNS or network issue that might cause Crowd unable to access your LDAP server easily. In some cases, the root cause of such issue could be due to network or communication issue between Crowd and the LDAP server.

Hope it helps.

Cheers,
Septa Cahyadiputra

Jiannan Tang January 9, 2013

Hi Septa:

Thanks your answer. I think the problem is the network, because I had setted the time out 3 minutes.

Septa Cahyadiputra
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 9, 2013

Yeap, that might be the cause. Hope your issue would be solve soon.

:)

0 votes
sathish February 1, 2015

hi team,

            i too facing the same issue and but we not at all did any changes in crowd may i know the root cause for this issue

 

thanks

sathish

AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 1, 2015

Hi Sathish, Issues on the network or on the LDAP side could cause timeouts, without your having made any changes in Crowd. Cheers, Ann

0 votes
Guardian News & Media June 12, 2013

I mean, is there any possibility that this is Java / Crowd related and not just "network"?

Sergio November 27, 2013

Did you resolve your problem? I might have the same one.

Thanks.

0 votes
Jiannan Tang January 9, 2013

Crowd Version: 2.5.3

JIRA v5.2.1

Suggest an answer

Log in or Sign up to answer