We have a user who recently had their name changed. Since then, they hvae not been able to sync across to confluence from our on prem AD server (configured in confluence to automatically pull from a specific OU where the user is sitting). We have troubleshooted to a point where we want to attempt some of the steps in the link below, but want to ensure this statement doesn't apply to us:
If the directory (where users are located) is using a Confluence local groups, do not use the below resolution steps, but reach out to Atlassian Support. The below steps will corrupt groups membership in that case.
Hi @Isaiah Hind ,
My recommendation would still be to reach out to Atlassian Support before proceeding, just to be sure.
I haven't worked with DC and IdP syncs, but I do this often in the cloud.
Anyway, based on the docs, if you have any local groups (even if you're using the mirrored LDAP directory method), you'll have to rebuild all local groups and manually restore users to each group afterward.
Again, just to 'play it safe,' you could check with the official support team what you can additionally check before you proceed with the linked workaround 🤔
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.