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:
(&(&(objectClass=group)(memberOf=CN=confluence-user,OU=Confluence,OU=Company,DC=en))))
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:
(&(objectCategory=person)(objectClass=user)(memberOf:1.2.840.113556.1.4.1941:=CN=confluence-Test,OU=Confluence,OU=Company,DC=en))
@Doc Snuggles Welcome to the Atlassian community.
Depending on the version of Confluence that you are on it might not support nested AD groups. Even after they added support for nested groups it needs to be configured and it only works a certain way. More information can be found here: https://confluence.atlassian.com/adminjiraserver/managing-nested-groups-938847047.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.