We are using the memberOf plugin in a global, multi-master-multi-slave setup, and so far we have not encountered any major issues. You can easily change the membership attribute, for example, to memberUid. MMR is handled by not replicating the memberOf attribute between masters, but the attribute IS copied to slaves. Each master runs own instance of the plugin. Sometimes you may need to manual launch the fix-up task, but that has been quite rare. If necessary, you can schedule it to run periodically. -- Lars Remes / Service Quality lars.remes@xxxxxxxxxx www.symbio.com > -----Original Message----- > From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users- > bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Vesa Alho > Sent: 21. lokakuuta 2013 13:23 > To: General discussion list for the 389 Directory server project. > Subject: MemberOf Plugin - experiences? > > Hi, > > I have a commercial application which could use MemberOf information > from LDAP (ref http://directory.fedoraproject.org/wiki/MemberOf_Plugin). > Does many people use this plugin and what are your experiences with it? > Currently we are only using "uniquemember" attribute in Group entries. > > Some stuff on the Issues list look worrying to me: > > "Membership attribute is currently hard-coded to be "member"" > "We really should make this work with MMR. " > > MemberOf is not crucial to us. So, before I start experimenting, it > would be great to know if it's "worth" my time. > > -Mr. Vesa Alho > -- > 389 users mailing list > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
