Hi, 389-ds has an access control mechanism which allows fine grained access to entries, attributes for different types of operation and based on various criteria like d,n group membership, role,.... and you should get familiar with the basics before just adding specific acis: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/managing_access_control for your specific request you could do something like: dn: l=kranj,c=si aci: (targetattr = "*")(version 3.0; acl "Admin rights"; allow( all ) userdn = "ldap:///uid=mnadmin,ou=user,l=Kranj,c=si";) not that in 389-ds acis have to be placed at the top of the subtree they should apply Ludwig On 06/22/2017 12:31 PM, Kalan Blaz
wrote:
-- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander |
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx