Same user names in local DB and Active Directory - How to switch to AD?

[Sascha Backes]

Hey guys,

our Confluence was restricted to a single AD group in the beginning (5 Users). To have more people collaborate, local users where created with the same username as in the Active Directory. Those users did also collaborate with articles. Now we want Confluence open for all users and therefore removed the group-limitations from the LDAP-binding.

What can I do to migrate/ remove my 4-5 local users and have them authenticate against LDAP? Removing is impossible according to Confluence, because, as said, they did write articles.

Thanks in advance!

[PeterKoczan · Accepted solution]

Dirk is right on his suggestion. If you change the directory order, your user will be authenticated against the first directory. If the username in this directory is the same as in other directories, apart from group memberships, all permissions will be the same for that user and content created will relate to him.

The general idea you have to consider is that the username is the primary key for identifying an user, regardless of the authentication method.

[Sascha Backes]

Sorry for the late reply, but Peter's suggestion was right. Thank you all for your quick help!

Cheers

[dirkd]

Can't you just remove your limitation to one LDAP group and then put the AD before the "Confluence Internal Directory"? IIRC then first the AD will be used to authenticate.

[Hemal Udani]

It is actually very simple. Create the same account in the LDAP directory. And immediately delete the accounts in the non-LDAP directory. This worked for me with Crowd. If you are using Confluence only and not Crowd, this may not work.