Bookmark this page

Guided Exercise: Managing Automation Controller Access with Teams

  • Organize users into teams and explore the access provided by different team roles.

Outcomes

  • Organize users into teams.

  • Assign different roles to team members.

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-team

Procedure 2.2. Instructions

  1. Create a new team called Developers.

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

    2. Navigate to AccessTeams and then click Add.

    3. Create the team using the following information:

      FieldValue
      Name Developers
      Description Dev Team
      Organization Default
    4. Click Save to create the new team.

  2. Create the daniel user.

    1. Navigate to AccessUsers and then click Add.

    2. Create the new user with the following information:

      FieldValue
      First Name Daniel
      Last Name George
      Email daniel@lab.example.com
      Username daniel
      Password redhat123
      Confirm Password redhat123
      User Type Normal User
      Organization Default

      Note

      The user type is set to Normal User rather than System Administrator. The daniel user will be an administrator of the Developers team, but the user will not be assigned administrative capabilities on the entire automation controller instance.

    3. Click Save to create the new user.

  3. Assign the daniel user the Admin role on the Developers team.

    1. Navigate to AccessTeams and then click the link for the Developers team.

    2. Click the Access tab and then click Add.

    3. Click Users and then click Next.

    4. Select daniel and then click Next.

    5. Select Admin and then click Save to assign the role.

  4. Create the donnie user.

    1. Navigate to AccessUsers and then click Add.

    2. Create the new user with the following information:

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

  5. Assign the donnie user the Read role on the Developers team.

    1. Navigate to AccessTeams and then click the link for the Developers team.

    2. Click the Access tab and then click Add.

    3. Click Users and then click Next.

    4. Select donnie and then click Next.

    5. Select Read and then click Save to assign the role.

  6. Create the david user and associate the user with the Developers team. Associating the user adds the Member role for the team.

    1. Navigate to AccessUsers and then click Add.

    2. Create the new user with the following information:

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

    4. On the Details page for the david user, click the Teams tab and then click Associate.

    5. Select Developers and then click Save to assign the Member role.

    6. Click adminLogout to exit the automation controller web UI.

  7. Verify the permissions for the daniel user.

    1. Log in to the automation controller web UI as daniel with redhat123 as the password.

    2. Navigate to AccessTeams and then click the link for the Developers team.

      Notice that the Edit button is available, indicating that the daniel user can make changes to the Developers team.

    3. Click the Access tab.

      Notice that the Add button is available and that each existing role assignment for members of the Developers team contains an X, indicating that the role assignment can be removed. The daniel user can manage permissions for the Developers team. Having the Admin role additionally allows the daniel user to inherit permissions assigned to the Developers team.

    4. Click danielLogout to exit the automation controller web UI.

  8. Verify the permissions for the donnie user.

    1. Log in to the automation controller web UI as donnie with redhat123 as the password.

    2. Navigate to AccessTeams and then click the link for the Developers team.

    3. Click the Access tab.

      Notice that the Add button is not available and that each existing role assignment does not contain an X, indicating that the role assignment cannot be removed. The donnie user can view information about the Developers team, but the user cannot make changes to it. Additionally, by only having the Read role, the donnie user does not inherit permissions assigned to the Developers team.

    4. Click donnieLogout to exit the automation controller web UI.

  9. Verify the permissions for the david user.

    1. Log in to the automation controller web UI as david with redhat123 as the password.

    2. Navigate to AccessTeams and then click the link for the Developers team.

    3. Click the Access tab.

      Notice that the Add button is not available and that each existing role assignment does not contain an X, indicating that the role assignment cannot be removed. Like the donnie user, the david user can view information about the Developers team, but the user cannot make changes to it. Unlike the donnie user, having the Member role allows the david user to inherit permissions assigned to the Developers team.

    4. Click davidLogout to exit 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-team

This concludes the section.

Revision: do467-2.2-08877c1