After upgrading from 5.7.1 to 7.13.2 the confluence-user group is no longer updated

[Ramy]

Hi all

Since upgrading our confluence server from version 5.7.1 to 7.13.2 I have a very strange behavior. The confluence-user group is not updated anymore.

We are using Active Directory and have not changed the configuration on either side (AD and Confluence server). 

The connection on the Confluence server to AD is synchronized regularly. New users are available locally on the Confluence server and are assigned to different groups. They are only missed in the confluence-user group! Therefore, they can access confluence but not the Spaces because the administrators of the Spaces are not able to add the user to their Spaces.

Do you have any idea what is going wrong here? I will be grateful for any help.

Thanks in advance

Ramy

[Clark Everson]

Hi @Ramy 

Have you attempted to completely remove the previous LDAP Active Directory configuration and re-add it? If not, there are major differences between confluence 5.7.1 and 7.13.2 both tooling and architecturally speaking, it isn't a straightforward upgrade.

I would recommend setting up the Active Directory sync from scratch.

https://confluence.atlassian.com/doc/connecting-to-an-ldap-directory-229838241.html

Best,

Clark

[Ramy]

Hi @Clark Everson 

Thank you very much for your answer. Honestly, I did not know about this. The Atlassian engineer who assisted me during the upgrade process never told me about this tip.

I will look at it and try it out in the next few days and let you know if it solved my problem.

Thank you very much (y)

Best,

Ramy

[Clark Everson]

No problem, honestly it's easy to overlook. Some things are taken for granted. i just remember even when we moved to cloud at my old company or have done migrations at my current company often times LDAP needs to be reset up even on the same versions, so different versions are a completely different ball game!

[Ramy]

Hi @Clark Everson 

A question about users and groups. If I remove the existing (old) directory and create a new one. The new directory will have a new directory ID and new user and group IDs.

Therefore, all existing users will lose their access to the current spaces. Am I correct or did I misunderstand something?

Thank you and best regards

Ramy 

[Clark Everson]

Hi @Ramy 

You should always test this is in a staging environment before doing in production to check any of these issues.

I am unsure myself but that's also because at every org i worked at we used a plugin to do this nothing built by Atlassian except Cloud.

Best,

Clark