Configure credentials to authenticate remote systems and services
Credentials authenticate the automation controller user when launching jobs against machines, synchronizing with inventory sources, and importing project content from a version control system.
You can grant users and teams the ability to use these credentials, without exposing the credential to the user. If a user moves to a different team or leaves the organization, you do not have to re-key all of your systems just because that credential was available in automation controller.
Automation controller encrypts passwords and key information in the database and never makes secret information visible through the API.
- How credentials work
Credentials in automation controller store the information required to authenticate to remote systems and services. Credentials include usernames and passwords, SSH keys, tokens, and other sensitive data. Automation controller encrypts sensitive credential data in the database to enhance security. - Credential types
Ansible Automation Platform supports a number of credential types. - Use automation controller credentials in a playbook
You can access automation controller credentials in an Ansible Playbook by using environment variables. You can get credential parameters from a job runtime environment: - Custom credential types
As a system administrator, you can define a custom credential type in a standard format by using a YAML or JSON-like definition. You can define a custom credential type that works in ways similar to existing credential types. - Add new users and job templates to existing credentials
You can add new users and job templates to existing credentials in automation controller. - Getting started with credential types
Explore how automation controller organizes authentication details by using custom credential types. Reviewing existing definitions helps ensure you configure new credentials accurately for your automation tasks.