-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
2
-
1
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Pace USER-105 we should support dynamic groups where a group has an attribute which is an LDAP filter.
[CONFSERVER-8046] Support real dynamic groups
R K
added a comment - Despite from what is says in the documentation this is not yet supported.
This is needed so we can use Confluence with our LDAP that uses dynamic groups on a per-user basis.
Please let me know in case you want a copy of our LDAP schema for testing purposes
R K
added a comment - Despite from what is says in the documentation this is not yet supported.
This is needed so we can use Confluence with our LDAP that uses dynamic groups on a per-user basis.
Please let me know in case you want a copy of our LDAP schema for testing purposes 
jeff peichel
added a comment - On this page: http://confluence.atlassian.com/display/DEV/How+to+map+LDAP+Users+and+Groups+to+Confluence+via+Atlassian+User
It seems to indicate that dynamic groups are supported, however it is not document exactly how its supposed to work. The example given relies on the fact that you are using Active Directory. AD is the only directory server that uses the memberOf attribute at the user level, which is really not how dynamic groups work in other directories like Sun's directory.
In those cases, dynamic groups are defined with a memberURL like this:
dn: cn=All EMEA Users - Dynamic, ou=Groups, ou=Partners, ou=External, o=SDS
memberurl: ldap:///ou=Partners,ou=External,o=SDS??sub?(&(objectclass=organiza
tionalPartner)(|(countrycode=GB)(countrycode=DE)(countrycode=IT)(countrycode=FR)))
objectclass: top
objectclass: groupofuniquenames
objectclass: groupofurls
cn: All EMEA Users - Dynamic
jeff peichel
added a comment - On this page: http://confluence.atlassian.com/display/DEV/How+to+map+LDAP+Users+and+Groups+to+Confluence+via+Atlassian+User
It seems to indicate that dynamic groups are supported, however it is not document exactly how its supposed to work. The example given relies on the fact that you are using Active Directory. AD is the only directory server that uses the memberOf attribute at the user level, which is really not how dynamic groups work in other directories like Sun's directory.
In those cases, dynamic groups are defined with a memberURL like this:
dn: cn=All EMEA Users - Dynamic, ou=Groups, ou=Partners, ou=External, o=SDS
memberurl: ldap:///ou=Partners,ou=External,o=SDS??sub?(&(objectclass=organiza
tionalPartner)(|(countrycode=GB)(countrycode=DE)(countrycode=IT)(countrycode=FR)))
objectclass: top
objectclass: groupofuniquenames
objectclass: groupofurls
cn: All EMEA Users - Dynamic
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center