-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Couldn't it be because you disallow access preceding this particular ACL? ACLs are read rule-by-rule thus they're are position dependent in slapd.conf I also don't use 'exact' but just 'dn'. If that's (some sort of) a mistake, please, feel free to correct me :)
Hi, Zdenek
Thanks for the reply. Makes sense, and it was my bad not to post all my rules.
So, my slapd.conf is like that:
access to attrs=userPassword,shadowLastChange by anonymous auth by dn.exact="cn=Admin,dc=domain,dc=org" write by self read by self write by * read
access to dn.subtree="ou=FTPUsers,dc=domain,dc=org" by dn.exact="cn=Admin,dc=domain,dc=org" write by dn.exact="uid=crud,ou=Applications,dc=domain,dc=org" write by self write by * read
access to * by dn.exact="cn=Admin,dc=domain,dc=org" write by self write by * read
Do you (or somebody) thinks that that by * read before FTPUsers rule can "kill" the uid=crud write ACL ?
I never used just 'dn', but I don't think this is an error. I will test some rule orders and dn without exact as soon as I finish the meeting I am in and I'll post my results.
CheerS
- --
.0. MrBiTs - mrbits.dcf@gmail.com ..0 GnuPG - http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6EC818FC2B3CA5AB 000 http://www.mrbits.com.br