Internal directory with LDAP authentication

I want to impliment a second LDAP authentication directory to another domain and to avoid the issues of users with the same name would like to use a domain suffix for the users login.

Currently I have users across both LDAP directories with the same samaccountname which means the LDAP auth directory with the higest priority wins.

Is this possible - or should I be looking at another route? If so, which path should I follow.

2 answers

We currently use the sAMAccountName attribute. I wonder if I look at using the users UPN which would then avoid this issue. Is anyone using this attribute?

Hi Sean, changing the LDAP attribute used for usernames in JIRA seems the best path to follow. Some companies decide to use the mail attribute, instead of sAMAccountName.

There only two things you should pay attention when changing the attribute, it should always return an unique value (two LDAP objects retuning the same username would break the synchronization) and it can't return a null value.

I hope it helps.


Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

172 views 1 17
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you