Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,296,263
Community Members
 
Community Events
165
Community Groups

can't connect crowd to ldap

hello.

in crowd, i pressed 'add directory'

i defined the connector, tested it and it worked.

i then defined the configuration, set the timeout to be very long and clicked 'test'

nothing happens for a while and then a blank page loads in the browser with the url:

http://wiki-upgrade:8095/crowd/console/secure/directory/testPrincipalSearch!testPrincipalSearch.action

the logs only have one line in them:

2012-08-08 18:20:42,995 http-8095-5 WARN com.opensymphony.xwork.DefaultActionInvocation No result defined for action com.atlassian.crowd.console.action.directory.CreateConnector and result input

i did tcpdump on port 389, and there is definetly activity there.

3 answers

Hi Gregory,

Good to know that the problem is solved now. If you experience any other problem please feel free to raise a support ticket at our support.atlassian.com and we will be glad to help you.

Cheers,

LJ.

what solved the problem for me was downgrading from crowd 2.5 to 2.4.1

I'm having exactly the same issue. I've enabled debug logging and I see a timeout:

2012-12-10 20:30:21,075 Timer-0 DEBUG [mchange.v2.resourcepool.BasicResourcePool] EXPIRED idle resource: com.mchange.v2.c3p0.impl.NewPooledConnection@19e8dd7a ---> idle_time: 35045; max_idle_time: 30000 [com.mchange.v2.resourcepool.BasicResourcePool@2bf525ec
2012-12-10 20:30:21,076 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 DEBUG [v2.c3p0.impl.C3P0PooledConnectionPool] Preparing to destroy PooledConnection: com.mchange.v2.c3p0.impl.NewPooledConnection@19e8dd7a
2012-12-10 20:30:21,078 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 DEBUG [v2.c3p0.impl.NewPooledConnection] com.mchange.v2.c3p0.impl.NewPooledConnection@19e8dd7a closed by a client.
java.lang.Exception: DEBUG -- CLOSE BY CLIENT STACK TRACE
	at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:566)
2012-12-10 20:30:21,080 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0 DEBUG [mchange.v2.resourcepool.BasicResourcePool] Successfully destroyed resource: com.mchange.v2.c3p0.impl.NewPooledConnection@19e8dd7a
2012-12-10 20:30:33,880 http-8095-1 DEBUG [atlassian.xwork.interceptors.TransactionalInvocation] Committing transaction for action /console/secure/directory/testPrincipalSearch.action (CreateConnector.testPrincipalSearch())
2012-12-10 20:30:33,880 http-8095-1 DEBUG [atlassian.xwork.interceptors.TransactionalInvocation] Creating transaction for action result: /console/secure/directory/testPrincipalSearch.action (CreateConnector.testPrincipalSearch())
2012-12-10 20:30:33,880 http-8095-1 WARN [com.opensymphony.xwork.DefaultActionInvocation] No result defined for action com.atlassian.crowd.console.action.directory.CreateConnector and result input

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

314 views 0 10
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you