I found that very interesting, so I did some browsing and came up with the equivalent function for Redhat Directory Server / 389 Directory Server: http://www.redhat.com/docs/manuals/dir-server/8.2/admin/html/Advanced_Entry_Management.html#Advanced_Entry_Management-Using_Groups See section 11.1.4 Using the memberOf Attribute to Manage Group Membership Information
Thanks again for the tip! Daniel On Tue, Aug 31, 2010 at 2:56 PM, David Hawes <[email protected]> wrote: > On 8/30/10 12:45 PM, Daniel Bower wrote: >> You are correct, the directory structure does not follow that >> particular convention. >> >> I'm guessing that whatever tool you use to manage users in ldap would >> also have to ensure that data stays synched between the two trees, or >> else you'd quickly have a mess on your hands. I'll check into it, >> thanks for the tip. > > We have replication processes that ensure the data stays synced between > the two branches. > > Assuming you are using OpenLDAP, you could use the dynlist overlay to > automatically search the group branch and populate a member attribute > when a person is returned: > > http://www.openldap.org/doc/admin24/overlays.html#Dynamic%20Lists > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
