Bookmark this page

Guided Exercise: Creating and Managing Automation Controller Users

  • Create user accounts of different types and explore the different levels of access of those account types.

Outcomes

  • Create user accounts of different account types.

As the student user on the workstation machine, use the lab command to prepare your system for this exercise.

This command ensures that automation controller is installed.

[student@workstation ~]$ lab start org-user

Procedure 2.1. Instructions

  1. Navigate to https://controller.lab.example.com and log in as the admin user with redhat as the password.

  2. Create a user, sam, as a Normal User.

    1. Navigate to AccessUsers and then click Add.

    2. On the Create New User page, fill in the details as follows:

      FieldValue
      First Name Sam
      Last Name Simons
      Email sam@lab.example.com
      Username sam
      Password redhat123
      Confirm Password redhat123
      User Type Normal User
      Organization Default
    3. Click Save to create the new user.

  3. Verify the roles for the newly created sam user.

    1. Click the Roles tab to see the user’s roles.

    2. User sam has the Member role for the Default organization.

    3. Click adminLogout in the upper-right corner to log out and then log back in as the sam user with redhat123 as the password.

    4. User sam has limited access. In the left navigation, some items are not displayed, such as AdministrationNotifications, AdministrationManagement Jobs, AdministrationInstance Groups, and Settings.

    5. Navigate to AccessUsers. User sam cannot add, modify, or delete users. This user can update basic settings, such as the first name, last name, email, username, and password fields.

    6. Click samLogout in the upper-right corner to log out.

  4. Create a user, sylvia, as a System Auditor.

    1. Log back in as the admin user and use redhat as the password.

    2. Navigate to AccessUsers and then click Add.

    3. On the Create New User page, fill in the details as follows:

      FieldValue
      First Name Sylvia
      Last Name Simons
      Email sylvia@lab.example.com
      Username sylvia
      Password redhat123
      Confirm Password redhat123
      User Type System Auditor
      Organization Default
    4. Click Save to create the new user.

  5. Verify the roles for sylvia.

    1. Click the Roles tab to see the user’s roles. Notice that user sylvia has the System Auditor role.

    2. Log out and log back in as sylvia user with redhat123 as the password.

    3. The user sylvia has access to all elements, such Users, Teams, Projects, Credentials, and so on. Although the user can see all of the resources, the user cannot add, modify, delete, or use any of the resources.

    4. Navigate to AccessUsers. The user sylvia cannot add, modify, or delete users. This user can update basic settings, such as the first name, last name, email, username, and password fields.

    5. Click sylviaLogout in the upper-right corner to log out.

  6. Create a user, simon, as a System Administrator.

    1. Log back in as the admin user and use redhat as the password.

    2. Navigate to AccessUsers and then click Add.

    3. On the Create New User page, fill in the details as follows:

      FieldValue
      First Name Simon
      Last Name Stephens
      Email simon@lab.example.com
      Username simon
      Password redhat123
      Confirm Password redhat123
      User Type System Administrator
      Organization Default
    4. Click Save to create the new user.

  7. Verify the roles for simon.

    1. Click the Roles tab to see the user’s roles. This time the Roles page explicitly displays the message: System administrators have unrestricted access to all resources.

    2. Log out and log back in as simon user with redhat123 as the password.

    3. The user simon has access to all elements, such as Users, Teams, Projects, Credentials, and so on.

    4. Navigate to AccessUsers. The user simon can add, modify, and delete users.

    5. Click simonLogout to log out of the automation controller web UI.

Finish

On the workstation machine, change to the student user home directory and use the lab command to complete this exercise. This step is important to ensure that resources from previous exercises do not impact upcoming exercises.

[student@workstation ~]$ lab finish org-user

This concludes the section.

Revision: do467-2.2-08877c1