Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

OpenLDAP connector "password encryption" setting and authn


When configuring the OpenLDAP directory connector connection configuration in Crowd, there is a section labeled "password encryption" (which should be re-labeled password hashing btw)...

When one has a directory connection for OpenLDAP how does authn in crowd actually work?

1) Is crowd just doing an LDAP bind against the target directory and letting the ldap server handle the hash comparison internally?


2) is crowd loading the LDAP record's userPassword attribute and doing its own hash and comparison within crowd itself?

I see the "password encryption" available options are DES, MD5, PLAINTEXT, SHA, SSHA. What effect does changing this option affect?

If the authn method is (1) above, why is this even relevant unless crowd is mutating users in the configured LDAP?

Why is the list of options for "password encryption" limited to this set of algorithms. When OpenLDAP supports many more than this. What decides what shows up in this list?


0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events