Language:
Format:

Language:
Format:

Red Hat Training

A Red Hat training course is available for RHEL 8

Chapter 15. Managing user groups using Ansible playbooks

This section introduces user group management using Ansible playbooks.

A user group is a set of users with common privileges, password policies, and other characteristics.

A user group in Identity Management (IdM) can include:

IdM users
other IdM user groups
external users, which are users that exist outside of IdM

The section includes the following topics:

15.1. The different group types in IdM

IdM supports the following types of groups:

POSIX groups (the default)

POSIX groups support Linux POSIX attributes for their members. Note that groups that interact with Active Directory cannot use POSIX attributes.

POSIX attributes identify users as separate entities. Examples of POSIX attributes relevant to users include uidNumber, a user number (UID), and gidNumber, a group number (GID).

Non-POSIX groups

Non-POSIX groups do not support POSIX attributes. For example, these groups do not have a GID defined.

All members of this type of group must belong to the IdM domain.

External groups

Use external groups to add group members that exist in an identity store outside of the IdM domain, such as:

A local system
An Active Directory domain
A directory service

External groups do not support POSIX attributes. For example, these groups do not have a GID defined.

Table 15.1. User groups created by default

Group name	Default group members
`ipausers`	All IdM users
`admins`	Users with administrative privileges, including the default `admin` user
`editors`	This is a legacy group that no longer has any special privileges
`trust admins`	Users with privileges to manage the Active Directory trusts

When you add a user to a user group, the user gains the privileges and policies associated with the group. For example, to grant administrative privileges to a user, add the user to the admins group.

Warning

Do not delete the admins group. As admins is a pre-defined group required by IdM, this operation causes problems with certain commands.

In addition, IdM creates user private groups by default whenever a new user is created in IdM. For more information about private groups, see Adding users without a private group.

15.2. Direct and indirect group members

User group attributes in IdM apply to both direct and indirect members: when group B is a member of group A, all users in group B are considered indirect members of group A.

For example, in the following diagram:

User 1 and User 2 are direct members of group A.
User 3, User 4, and User 5 are indirect members of group A.

Figure 15.1. Direct and Indirect Group Membership

A chart with Group A (with 2 users) and Group B (with 3 users). Group B is nested inside Group A so Group A contains a total of 5 users.

If you set a password policy for user group A, the policy also applies to all users in user group B.

15.3. Ensuring the presence of IdM groups and group members using Ansible playbooks

The following procedure describes ensuring the presence of IdM groups and group members - both users and user groups - using an Ansible playbook.

Prerequisites

You know the IdM administrator password.
You have installed the ansible-freeipa package on the Ansible controller.
The users you want to reference in your Ansible playbook exist in IdM. For details on ensuring the presence of users using Ansible, see Managing user accounts using Ansible playbooks.

Procedure

Create an inventory file, for example inventory.file, and define ipaserver in it:
```
[ipaserver]
server.idm.example.com
```

Create an Ansible playbook file with the necessary user and group information:

---
- name: Playbook to handle groups
  hosts: ipaserver
  become: true

  tasks:
  - name: Create group ops with gid 1234
    ipagroup:
      ipaadmin_password: MySecret123
      name: ops
      gidnumber: 1234

  - name: Create group sysops
    ipagroup:
      ipaadmin_password: MySecret123
      name: sysops
      user:
      - idm_user

  - name: Create group appops
    ipagroup:
      ipaadmin_password: MySecret123
      name: appops

  - name: Add group members sysops and appops to group ops
    ipagroup:
      ipaadmin_password: MySecret123
      name: ops
      group:
      - sysops
      - appops

Run the playbook:

$ ansible-playbook -v -i path_to_inventory_directory/inventory.file path_to_playbooks_directory/add-group-members.yml

Verification steps

You can verify if the ops group contains sysops and appops as direct members and idm_user as an indirect member by using the ipa group-show command:

Log into ipaserver as administrator:

$ ssh admin@server.idm.example.com
Password:
[admin@server /]$

Display information about ops:

ipaserver]$ ipa group-show ops
  Group name: ops
  GID: 1234
  Member groups: sysops, appops
  Indirect Member users: idm_user

The appops and sysops groups - the latter including the idm_user user - exist in IdM.

Additional resources

See the /usr/share/doc/ansible-freeipa/README-group.md Markdown file.

15.4. Ensuring the presence of member managers in IdM user groups using Ansible playbooks

The following procedure describes ensuring the presence of IdM member managers - both users and user groups - using an Ansible playbook.

Prerequisites

You know the IdM administrator password.
You have installed the ansible-freeipa package on the Ansible controller.
You must have the name of the user or group you are adding as member managers and the name of the group you want them to manage.

Procedure

Create an inventory file, for example inventory.file, and define ipaserver in it:
```
[ipaserver]
server.idm.example.com
```

Create an Ansible playbook file with the necessary user and group member management information:

---
- name: Playbook to handle membership management
  hosts: ipaserver
  become: true

  tasks:
  - name: Ensure user test is present for group_a
    ipagroup:
      ipaadmin_password: MySecret123
      name: group_a
      membermanager_user: test

  - name: Ensure group_admins is present for group_a
    ipagroup:
      ipaadmin_password: MySecret123
      name: group_a
      membermanager_group: group_admins

Run the playbook:

$ ansible-playbook -v -i path_to_inventory_directory/inventory.file path_to_playbooks_directory/add-member-managers-user-groups.yml

Verification steps

You can verify if the group_a group contains test as a member manager and group_admins is a member manager of group_a by using the ipa group-show command:

Log into ipaserver as administrator:

$ ssh admin@server.idm.example.com
Password:
[admin@server /]$

Display information about managergroup1:

ipaserver]$ ipa group-show group_a
  Group name: group_a
  GID: 1133400009
  Membership managed by groups: group_admins
  Membership managed by users: test

Additional resources

See ipa host-add-member-manager --help.
See the ipa man page.

15.5. Ensuring the absence of member managers in IdM user groups using Ansible playbooks

The following procedure describes ensuring the absence of IdM member managers - both users and user groups - using an Ansible playbook.

Prerequisites

You know the IdM administrator password.
You have installed the ansible-freeipa package on the Ansible controller.
You must have the name of the existing member manager user or group you are removing and the name of the group they are managing.

Procedure

Create an inventory file, for example inventory.file, and define ipaserver in it:
```
[ipaserver]
server.idm.example.com
```

Create an Ansible playbook file with the necessary user and group member management information:

---
- name: Playbook to handle membership management
  hosts: ipaserver
  become: true

  tasks:
  - name: Ensure member manager user and group members are absent for group_a
    ipagroup:
      ipaadmin_password: MySecret123
      name: group_a
      membermanager_user: test
      membermanager_group: group_admins
      action: member
      state: absent

Run the playbook:

$ ansible-playbook -v -i path_to_inventory_directory/inventory.file path_to_playbooks_directory/ensure-member-managers-are-absent.yml

Verification steps

You can verify if the group_a group does not contain test as a member manager and group_admins as a member manager of group_a by using the ipa group-show command:

Log into ipaserver as administrator:

$ ssh admin@server.idm.example.com
Password:
[admin@server /]$

Display information about group_a:

ipaserver]$ ipa group-show group_a
  Group name: group_a
  GID: 1133400009

Additional resources

See ipa host-remove-member-manager --help.
See the ipa man page.

Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

Red Hat Training

Chapter 15. Managing user groups using Ansible playbooks

15.1. The different group types in IdM

15.2. Direct and indirect group members

15.3. Ensuring the presence of IdM groups and group members using Ansible playbooks

15.4. Ensuring the presence of member managers in IdM user groups using Ansible playbooks

15.5. Ensuring the absence of member managers in IdM user groups using Ansible playbooks

Language and Page Formatting Options

Red Hat Training

Chapter 15. Managing user groups using Ansible playbooks

15.1. The different group types in IdM

15.2. Direct and indirect group members

15.3. Ensuring the presence of IdM groups and group members using Ansible playbooks

15.4. Ensuring the presence of member managers in IdM user groups using Ansible playbooks

15.5. Ensuring the absence of member managers in IdM user groups using Ansible playbooks