Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Synchronisation AD with Confluence

Doc Snuggles
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 10, 2023

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:


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events