You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We had users failing to authenticate with all-lowercase characters, but once we had them login with mixed-case, authentication succeeded. Since Active Directory is not case-sensitive in its searches, does this mean Bamboo is doing a case-sensitive compare on the results?
If so, can this be managed? Case-insensitive is preferred.
Hello @Robert Kerr,
If you have connected you LDAP into Crowd, then manage user authentication in Bamboo through Crowd, you can force all authentication in Crowd to be lowercase (Enforcing Lower-Case Usernames and Groups for an Application)
If you are managing Bamboo's authentication directly from LDAP, you cannot force lowercase authentication in Bamboo.
Note: If you have already defined user (e.g. JSmyth) or group (e.g MyGroup) permission in Bamboo and later you change authentication case to lowercase (e.g. jsmyth and/or mygroup), Bamboo will still granting permissions to initial set up, requiring to grant permission to new username and/group)
Kind regards,
Rafael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.