Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 2. Getting started as a platform administrator
As a platform administrator, Ansible Automation Platform can help you enable your users and teams to develop and run automation.
This guide walks you through the basic steps to get set up as an administrator for Ansible Automation Platform, including configuring and maintaining the platform for users.
To get started as an administrator, see the following:
2.1. Logging in for the first time Link kopierenLink in die Zwischenablage kopiert!
Log in to the Ansible Automation Platform as an administrator and enter your subscription information. You can then create user profiles and assign roles.
Procedure
-
With the login information provided after your installation completed, open a web browser and log in to Red Hat Ansible Automation Platform by navigating to the server URL at:
https://<AAP_SERVER_NAME>/ Use the credentials specified during the installation process to login:
- The default username is admin.
- The password for admin is the value specified during installation.
Next steps
After your first login, you are prompted to add your subscription information.
2.2. Adding a subscription Link kopierenLink in die Zwischenablage kopiert!
To add your subscription information, you can either upload your subscription manifest, or use your service account credentials to find the subscription associated with your account.
Prerequisites
To add your subscription by uploading a subscription manifest, you must first:
- Obtain your manifest file. See Obtaining a manifest file for more information.
To add your subscription using your service account credentials, you must first:
- Have created a service account and saved the client ID and client secret.
- Add your service account to the Subscription viewer user group to give it the ability to see your subscriptions. See the "Updates to subscription management" section in the Knowledgebase article Configure Ansible Automation Platform to authenticate through service account credentials for instructions on how to do so.
Procedure
To add your subscription by uploading a subscription manifest:
- Drag the file to the field beneath Red Hat subscription manifest or browse for the file on your local machine.
To add your subscription with your service account credentials:
- Click the Service Account tab.
- Enter the client ID you received when you created your service account in the field labeled Client ID.
Enter the client secret you received when you created your service account in the field labeled Client secret.
Your subscription appears in the Subscription list.
Select your subscription and click .
- Check the box indicating that you agree to the End User License Agreement.
- Review your information and click .
Troubleshooting
If you enter your client ID and client secret but cannot locate your subscription, you might not have the correct permissions set on your service account. For more information and troubleshooting guidance for service accounts, see Configure Ansible Automation Platform to authenticate through service account credentials.
2.3. Configure authentication Link kopierenLink in die Zwischenablage kopiert!
After your first login as an administrator, begin configuring authentication for your users. Depending on your organization’s needs and resources, you can either:
- Set up authentication by creating users, teams, and organizations, and then assigning them roles that govern access.
- Use an external source such as GitHub to configure authentication for your system.
The following sections serve as an introduction to authentication in Ansible Automation Platform. For more information on external authentication or using role-based access control, see the link:Access management and authentication guide.
2.4. Manage user access with role-based access control Link kopierenLink in die Zwischenablage kopiert!
Role-based access control (RBAC) restricts user access based on the user’s role within the organization they are assigned to in Ansible Automation Platform. The roles in RBAC refer to the levels of access that users have to Ansible Automation Platform components and resources.
Use RBAC to control what users can do with the components of Ansible Automation Platform at a broad or granular level. You can choose whether the user is a system administrator or normal user, and align roles and access permissions with their positions within the organization.
You can define roles with multiple permissions that can then be assigned to resources, teams, and users. The permissions that make up a role govern what the assigned role allows. Permissions are allocated with only the access needed for a user to perform the tasks appropriate for their role.
The following procedures show how to get started with RBAC by creating a team, and a user to assign to the team. For the complete workflow related to using RBAC to manage access, see the Access management and authentication guide, particularly the sections on Managing access with role-based access control and Roles.
When managing users, teams, and organizations, use the Unified UI or the platform gateway API to ensure real-time synchronization across all platform components, including Event-Driven Ansible controller. If you use the legacy automation controller API, changes can take up to 15 minutes to propagate to Event-Driven Ansible controller, which can result in authentication errors for new users or teams.
2.5. Creating an organization Link kopierenLink in die Zwischenablage kopiert!
Ansible Automation Platform automatically creates a default organization. If you have a self-support level license, you have only the default organization available and cannot delete it.
Procedure
-
From the navigation panel, select
. - Click .
Enter the Name and optionally provide a Description for your organization.
NoteIf automation controller is enabled on the platform, continue with Step 4. Otherwise, proceed to Step 6.
- Select the name of the Execution environment or search for one that exists that members of this team can run automation.
- Enter the name of the Instance Groups on which to run this organization.
- Optional: Enter the Galaxy credentials or search from a list of existing ones.
Select the Max hosts for this organization. The default is 0. When this value is 0, it signifies no limit. If you try to add a host to an organization that has reached or exceeded its cap on hosts, an error message displays:
You have already reached the maximum number of 1 hosts allowed for your organization. Contact your System Administrator for assistance.- Click .
If you selected more than 1 instance group, you can manage the order by dragging and dropping the instance group up or down in the list and clicking .
NoteThe execution precedence is determined by the order in which the instance groups are listed.
- Click and verify the organization settings.
- Click .
2.6. Creating a team Link kopierenLink in die Zwischenablage kopiert!
You can create new teams, assign an organization to the team, and manage the users and administrators associated with each team. Users associated with a team inherit the permissions associated with the team and any organization permissions to which the team has membership.
To add a user or administrator to a team, the user must have already been created.
Procedure
-
From the navigation panel, select
. - Click .
- Enter a Name and optionally give a Description for the team.
Select an Organization to be associated with this team.
NoteEach team can only be assigned to one organization.
Click .
The Details page opens, where you can review and edit your team information.
2.7. Creating a user Link kopierenLink in die Zwischenablage kopiert!
There are three types of users in Ansible Automation Platform:
- Normal user
- Normal users have read and write access limited to the resources (such as inventory, projects, and job templates) for which that user has been granted the appropriate roles and privileges. Normal users are the default type of user when no other User type is specified.
- Ansible Automation Platform Administrator
- An administrator (also known as a Superuser) has full system administration privileges, with full read and write privileges over the entire installation. An administrator is typically responsible for managing all aspects of and delegating responsibilities for day-to-day work to various users.
- Ansible Automation Platform Auditor
- Auditors have read-only capability for all objects within the environment.
Procedure
-
From the navigation panel, select
. - Click .
- Enter the details about your new user in the fields on the Create user page. Fields marked with an asterisk (*) are required.
Normal users are the default when no User type is specified. To define a user as an administrator or auditor, select a User type checkbox.
NoteIf you are modifying your own password, log out and log back in again for it to take effect.
- Select the Organization to be assigned for this user. For information about creating a new organization, see Creating an organization.
- Click .
Next steps
When the user is successfully created, the User dialog opens. From here, you can review and change the user’s Teams, Roles, Tokens and other membership details.
If the user is not newly-created, the details screen displays the last login activity of that user.
If you log in as yourself, and view the details of your user profile, you can manage tokens from your user profile by selecting the Tokens tab For more information, see Adding a token.