Comment #10 on issue 1491 by LDAP group support

Another ++ for this feature.

Use case:
- 1000 users in LDAP
- Users are part of LDAP groups based on their teams, etc.
- LDAP groups can be nested.
- Members of the LDAP groups have access to certain systems, repos, etc.

It is one thing to go into reviewboard and say anyone in this LDAP group has access to this repo. It is a maintenance nightmare if I also have to go in and manually configure the group memberships in reviewboard. LDAP is the certain of the world, why should I have to duplicate the configuration of who belongs to which group. Group membership can change over time, thus should not have to go an update all connected systems.


You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to