Chapter 21. Access control in IdM Access control defines the rights or permissions users have been granted to perform operations on other users or objects, such as hosts or services. Identity Management (IdM) provides several access control areas to make it clear what kind of access is being granted and to whom it is granted. As part of this, IdM draws a distinction between access control to resources within the domain and access control to the IdM configuration itself. This chapter outlines the different internal access control mechanisms that are available for IdM users both to the resources within the domain and to the IdM configuration itself. 21.1. Access control instructions in IdM The Identity Management (IdM) access control structure is based on the 389 Directory Server access control. By using access control instructions (ACIs), you can grant or deny specific IdM users access over other entries. All entries, including IdM users, are stored in LDAP. An ACI has three parts: Actor The entity that is being granted permission to do something. In LDAP access control models, you can, for example, specify that the ACI rule is applied only when a user binds to the directory using their distinguished name (DN). Such a specification is called the bind rule : it defines who the user is and can optionally require other limits on the bind attempt, such as restricting attempts to a certain time of day or a certain machine. Target The entry that the actor is allowed to perform operations on. Operation type Determines what kinds of actions the actor is allowed to perform. The most common operations are add, delete, write, read, and search. In IdM, the read and search rights of a non-administrative user are limited, and even more so in the IdM Web UI than the IdM CLI. When an LDAP operation is attempted, the following occurs: The IdM client sends user credentials to an IdM server as part of the bind operation. The IdM server DS checks the user credentials. The IdM server DS checks the user account to see if the user has a permission to perform the requested operation. 21.2. Access control methods in IdM Identity Management (IdM) divides access control methods into the following categories: Self-service rules Define what operations a user can perform on the user's own personal entry. This access control type only allows write permissions to specific attributes within the user entry. Users can update the values of specific attributes but cannot add or delete the attributes as such. Delegation rules By using a delegation rule, you can allow a specific user group to perform write, that is edit, operations on specific attributes of users in another user group. Similarly to self-service rules, this form of access control rule is limited to editing the values of specific attributes. It does not grant the ability to add or remove whole entries or control over unspecified attributes. Role-based access control Creates special access control groups that are then granted much broader authority over all types of entities in the IdM domain. Roles can be granted edit, add, and delete rights, meaning they can be granted complete control over entire entries, not just selected attributes. Certain roles are already available in IdM by default, for example Enrollment Administrator , IT Security Specialist , and IT Specialist . You can create additional roles to manage any types of entries, such as hosts, automount configuration, netgroups, DNS settings, and IdM configuration. Additional resources Using Ansible playbooks to manage self-service rules in IdM Delegating permissions to user groups to manage users using Ansible playbooks Using Ansible playbooks to manage role-based access control in IdM

Commands: