Crowd 2.7.2 with LDAPS

[Andrew Morin]

We recently had to switch to LDAPS from LDAP. Using LDAP we would see less than 10 connections to the LDAP server. We applied the settings from KB article...

https://confluence.atlassian.com/display/CROWDKB/Performance+problem+when+using+LDAPS

We are still seeing connections shoot up to over 5000 connections to the ldap server and users can no longer login to the applications.

On the Connector tab we have tried the following combinations.

1. ldap:// URL with SSL box ticked.
2. ldaps:// URL with SSL box ticked
3. ldaps:// without SSL box ticked

None seem to help. As soon as we switch back to ldap everything works fine...

Any idea's?

Thanks

Andrew

image2015-12-11 12:20:31.png ‏116 KB

[Mallmann · Accepted solution]

Hi Andrew,

The reported problem might be related to this bug that got fixed on Crowd 2.8.2: https://jira.atlassian.com/browse/CWD-4070

I'd recommend you to set up a staging environment in which you could upgrade Crowd to 2.8.2 and verify whether the problem is replicable there.

I hope it helps! 

Eduardo

[Andrew Morin]

We upgraded to 2.8.3 last night and it is working great now.

[Bruno Vincent]

Hi Andrew,

Did you check the LDAP connection pool settings?

https://confluence.atlassian.com/display/CROWD/Configuring+the+LDAP+Connection+Pool

You might also want to set your own values in setenv.sh:

-Dcom.sun.jndi.ldap.connect.pool.protocol='plain ssl'
-Dcom.sun.jndi.ldap.connect.pool.authentication='none simple DIGEST-MD5'
-Dcom.sun.jndi.ldap.connect.pool.maxsize = <your_value>
-Dcom.sun.jndi.ldap.connect.pool.prefsize = <your_value>
-Dcom.sun.jndi.ldap.connect.timeout = <your_value>