Years ago, we set up an Atlassian deployment (Jira, Confluence, Bamboo, Fisheye/Crucible, Crowd) completely integrated, but without any connection to our LDAP server.
Today, I'm asked to switch from an internal Crowd directory to a LDAP delegated authenticaton. Every Crowd user exists in our LDAP with the exact same username. Ideally, only the group membership shall be kept in Crowd, with the username definition and their password managed directly by the LDAP. As this solution does not seems to exist, delegated authenticaton is the way to go.
Is there an easy way to do so? I would think of the Crowd directory importer, but it requires that the password encryption are the same in both directory, though the goal of my operation is to drop the passwords...
Thanks for any help or suggestions.
PS: Currenty running Crowd 2.4, but an update is planned in the near futur.
This page details an (unsupported) work around for the problem of the encryption algorithms being different between an internal and delegated authentication directory: https://confluence.atlassian.com/pages/viewpage.action?pageId=391086175
There's a few relevant feature requests you might like to vote on:
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Do you own more than one Server or Data Center product? Do you have challenges provisioning users across your Atlassian products? Are you spending a lot of time integrating each Atlassian product wit...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs