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
Navigate to https://controller.lab.example.com and log in as the admin user with redhat as the password.
Create a user, sam, as a Normal User.
Navigate to → and then click .
On the page, fill in the details as follows:
| Field | Value |
|---|---|
| First Name |
Sam
|
| Last Name |
Simons
|
sam@lab.example.com
| |
| Username |
sam
|
| Password |
redhat123
|
| Confirm Password |
redhat123
|
| User Type |
Normal User
|
| Organization |
Default
|
Click to create the new user.
Verify the roles for the newly created sam user.
Click the tab to see the user’s roles.
User sam has the Member role for the Default organization.
Click → in the upper-right corner to log out and then log back in as the sam user with redhat123 as the password.
User sam has limited access. In the left navigation, some items are not displayed, such as → , → , → , and .
Navigate to → . 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.
Click → in the upper-right corner to log out.
Create a user, sylvia, as a System Auditor.
Log back in as the admin user and use redhat as the password.
Navigate to → and then click .
On the page, fill in the details as follows:
| Field | Value |
|---|---|
| First Name |
Sylvia
|
| Last Name |
Simons
|
sylvia@lab.example.com
| |
| Username |
sylvia
|
| Password |
redhat123
|
| Confirm Password |
redhat123
|
| User Type |
System Auditor
|
| Organization |
Default
|
Click to create the new user.
Verify the roles for sylvia.
Click the tab to see the user’s roles. Notice that user sylvia has the System Auditor role.
Log out and log back in as sylvia user with redhat123 as the password.
The user sylvia has access to all elements, such , , , , and so on. Although the user can see all of the resources, the user cannot add, modify, delete, or use any of the resources.
Navigate to → . 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.
Click → in the upper-right corner to log out.
Create a user, simon, as a System Administrator.
Log back in as the admin user and use redhat as the password.
Navigate to → and then click .
On the page, fill in the details as follows:
| Field | Value |
|---|---|
| First Name |
Simon
|
| Last Name |
Stephens
|
simon@lab.example.com
| |
| Username |
simon
|
| Password |
redhat123
|
| Confirm Password |
redhat123
|
| User Type |
System Administrator
|
| Organization |
Default
|
Click to create the new user.
Verify the roles for simon.
Click the tab to see the user’s roles. This time the page explicitly displays the message: System administrators have unrestricted access to all resources.
Log out and log back in as simon user with redhat123 as the password.
The user simon has access to all elements, such as , , , , and so on.
Navigate to → . The user simon can add, modify, and delete users.
Click → to log out of the automation controller web UI.