Jira Copy-on-first-login is changing users' names

We've been using Jira for a couple of years now and had a few hundred users in Jira under our deligated authentication directory to LDAP.

About a month ago, I enabled the copy-on-first-login option, so new users will be copied from LDAP the first time they login, if they don't already exist. I've started to notice that some of our existing users' names within Jira are being updated with the values from LDAP's cn attribute.

It's usually minor, like changing Ed to Edward, or adding a middle initial that wasn't included when they were manually added. But why did enabling copy-on-first-login cause Jira to start changing names for existing users??


6 answers

1 accepted

0 votes
Accepted answer

I believe I opened a case with Atlassian and was told this is just how it works. The name and email attributes are copied from LDAP on each login, not just the first. You just have to live with it.

0 votes

What did your configuration for "User First Name Attribute" says? Because of this issue, JIRA will not only copy users to be created on first login, but also copy users to be updated on next login.

I used:

"ldap.user.firstname": "givenName"
"ldap.user.lastname": "sn"

Is there a fix or workaround?

I haven't tested, but does this re-writing from LDAP only happen to existing users on their first login after enabling copy-on-first-login? Ie, after they've now logged in once, can I edit it back and have it stick? Or will it re-copy the name from LDAP each time?

0 votes

Because of the mentioned issue, it is most likely will re-copy ever time the user logged in. I would suggest to disable the Copy-on-first-login feature after all users already logged in. User that is to be added in the future can be included manually via the Admin UI.

We have about 50,000 active users in our LDAP and only about 200 in Jira. Any of these users could potentially log in at any point in the future. If I disabled Copy-on-first-login, I'd have to enable full directory sync of all users or install Crowd.

Is there no option to make Copy-on-first-login mean what it says, and only copy on first login, and not every login? Is there a fix coming for this?

Anyone know whether there is a workaround for this? Copy-on-first-login would enable a much more seamless way for users to first experience JIRA and remove the mundane job of dealing with user creation on an adhoc basis.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,672 views 18 21
Read article

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