We have a situation where we are creating a new AD groups for Confluence access for the first time in several years and the new groups are not coming over unless the users also have the "legacy" group.
For example, User A has had Confluence access for several years and is part of the "legacy" group. We can add User A to the "new" groups just fine, the groups show up under this user in Confluence as expected. We can also view the groups in the Confluence Admin side and those users show up in them as expected.
User B is a new user who is not a part of the "legacy" group. This user is a part of the "new" AD groups just like user A, but User B never shows up in the user list or group list after sync.
It looks like there is some issue between the "legacy" group and these new groups but we can't figure out what the difference is.
I've looked at licensing and we have plenty of licenses for these new users. I've also looked at the global permissions to ensure that all of these new groups have the "can use" box checked. Everything looks as expected in these areas.
Is there something that we're missing?
