How to start using LDAP without Internal directory users losing data?

[Kamil Beer]

Hello,

I saw a few similar threads, but none with an explicit solution to this problem:

We have 500 internal users and we would like to start using AD for an already existing base of users - these users are the same as in the internal directory. However, it seems that these users (if they have the same usernames in AD as in the internal directory, which is first in the directory order) will lose all their data on where are they assignees, their dashboards and so on - and will be taken as new users.

I am looking for a way to start using users in AD but without losing the data the same users have in the Internal directory (assignees and so on). So far, I didn't find an answer.

What is the proper way to go about this?

[Mikael Sandberg]

Hi @Kamil Beer

As long as the username is the same in both user directories the assignee data, dashboard owner, etc will not be lost. What they may have to do is setup their avatar again.

I just went through a user directory migration between two AD directories a couple of months ago, and had to use email addresses as a temporary username because we also changed usernames. The only thing that a user had to do after the migration was setting their avatar and changing any JQL queries that used the old username.

[Kamil Beer]

Alright, thank you!

[Kamil Beer]

Mikael, a strange thing happened to me: I have a Crowd instance that i tried to connect to our Jira. I have changed the internal user's username to "kamil.beer", just like in the Crowd instance, I put the Crowd instance as first in the directory order - only one kamil.beer account appeared (the one from the Crowd) - but the Crowd account had different issues assigned and different account details than the one from the Internal directory...

I would like to have the same data as the user had in the internal directory. What do you think I did wrong or what should I add? Any advice you might have is appreciated.

[Mikael Sandberg]

Hmm, almost sounds like there is an alias in Crowd that connects your user to a different one. If you go back to using the internal directory, do the issues that you saw when using Crowd have a different assignee?