Hi!
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?
Best regards,
Thomas
Confluence does not have such ability to filter out groups in UI only while still synchronizing those groups from LDAP server.
Do you have testing to configure the Additional Group DN like this:
cn:myWikiGroup,o
u=groups
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
eg. userSearchFilter
(&(objectCategory=Person)(sAMAccountName=*)(memberOf=cn=myWikiGroup,ou=wiki,ou=groups,ou=XXX,dc=XXX,dc=XXX,dc=XX))
Grettings
Jürgen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.