Thanks for the answer, found out that if I add user to group via group properties, LDAPAdmin put it in under attribute member, and if I add user to group via user properties, it add user under attribute memberUid. Is it possible somehow to say that member is equal to memberUid or how to persuade LDAPAdmin to put users directly under memberUid attribute? Bye, Alan solarflow99 pravi: > I use ldapadmin too, and reported a few bugs but I didn't notice this > one. I see that once you add a user to a group, all it does is add a > MemberUid attribute to the group, so I don't think it should matter > either way. I just tested this with samba, and it seems to work for > me, however i'm just using workgroups, not PDC ot ADS. The only thing > I can think of is the ldap group directive in smb.conf. > > ldap group suffix = ou=Groups > > > > > > On 4/2/08, *Alan Orli? Bel?ak* <alan.orlic at zd-lj.si > <mailto:alan.orlic at zd-lj.si>> wrote: > > Hello, > > I'm using LDAP Admin for administering our user database and > found out something strange, if I add user to group via group > properties, the permisions of that group aren't effective, but if > I add group to that user (via user properties), those permisions > are effective. Any ideas why? Looks like Samba and eGroupware are > checking only users and not groups. > > Bye, alan > > -- > Fedora-directory-users mailing list > Fedora-directory-users at redhat.com > <mailto:Fedora-directory-users at redhat.com> > https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >
