Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,467,515
Community Members
 
Community Events
177
Community Groups

Crowd 2.7.2 with LDAPS

Andrew Morin
Andrew Morin Rising Star Dec 11, 2015

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

 

Answer
Watch
Like Be the first to like this
653 views

2 answers

1 accepted

0 votes
Answer accepted
Mallmann
Mallmann Atlassian Team Dec 18, 2015

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! smile

Eduardo

View More Comments
Andrew Morin
Andrew Morin Rising Star Dec 18, 2015

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

Like
Reply
0 votes
Bruno Vincent
Bruno Vincent Rising Star Dec 12, 2015

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>
Reply

Suggest an answer

Log in or Sign up to answer
Crowd
Crowd
TAGS

Atlassian Community Events

See all events