You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello it's about connecting our AD and the groups there to Confluence, so that the AD groups can be used for permission control within Confluence.
Of course, the existing groups in AD should be used and the nested groups should also be used.
So, as I said. Wildcards don't work here because LDAP doesn't allow them. In Confluence, it's even more limited, because this query doesn't return anything. No idea why.
In short; LDAP (in AD) can read groups in groups, but then only in ONE named group:
Confluence can't do anything with it, but I don't know why. Because the technology is in AD, or so I thought.
What Confluence can do is read users from groups that are themselves members of a group: