I'm having the following pseudo LDAP-structure:
ou=groups |_ou=internal | | | |_cn:myInternalGroup | member:uid=foo | | | |_ou=wiki | |_cn:myWikiGroup member:cn:myInternalGroup,ou=internal,ou=groups
The internal tree is full of groups that are irrelevant for Wiki-users, so I want to limit the groups that are shown in the UI to only "ou=wiki".
The problem is that if I add a "Group Object Filter", confluence is not able to resolve the subgroup, as it sits under ou=internal.
How can I hide groups from the user interface without breaking the nesting of groups that are necessary to resolve membership?
I had the same problem. You can find a documention and create a filter based on the structure of your directory: https://confluence.atlassian.com/display/DEV/How+to+write+LDAP+search+filters
Thanks for your reply, but if I understand you correctly, this still does not solve my problem, as it would also prevent confluence to resolve the subgroups (which resides in the tree I'm trying to hide).
From the documentation: " In essence the filter limits what part of the LDAP tree Confluence syncs from"
I still need confluence to sync from the "internal"-tree, but I don't want to show the "internal" groups in the User Interface when end-users search for groups.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG