Chapter 6. Authentication movement
During an upgrade from Ansible Automation Platform 2.4 to 2.6, only complete authentication provider configurations are migrated to the new platform gateway.
A configuration is considered complete when it meets the following criteria:
- LDAP: You must specify a server URL.
- GitHub and Microsoft Azure AD: You must specify both a key and a secret.
- OIDC: You must define a key, a secret, and an OIDC endpoint.
- RADIUS and TACACS+: You must specify the host.
Before proceeding with the upgrade, ensure that you complete the following steps:
- Create a local administrator account and verify that you can log in to the environment using local authentication. You can also use the default administrator account from the inventory file.
- Enable the local authenticator in the target environment to ensure a fallback login method is available.
Perform a full backup of your existing environment.
ImportantThis is a critical step for data recovery in case any issues occur during the migration process.
Post upgrade
- Update the callback URLs in your Identity Provider (IdP) configurations after the movement. This is necessary for OAuth and SSO providers to function correctly with the new platform gateway architecture. For more information, see Updating callback URLs for OAuth and SSO providers.
- Reestablish custom certificates for LDAPS if your LDAP authentication uses custom certificates in the system’s trust store. This configuration is not automatically migrated and you must manually reestablish it.
The movement of existing authentication configurations from a Red Hat Ansible Automation Platform 2.4 automation controller to the new 2.6 platform gateway is automated. The following tables show how settings and mappings from the old automation controller schema are transformed to fit the new platform gateway API schema.
6.1. Authentication type: OIDC Copy linkLink copied to clipboard!
General settings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
SOCIAL_AUTH_OIDC_KEY: "client-id" SOCIAL_AUTH_OIDC_SECRET: “client-secret" SOCIAL_AUTH_OIDC_OIDC_ENDPOINT: "https://idp.example.com" SOCIAL_AUTH_OIDC_VERIFY_SSL: true
|
|
Mappings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
AUTH_LDAP_ORGANIZATION_MAP: "LDAP Organization": users: true
|
|
SOCIAL_AUTH_SAML_USER_FLAGS_BY_ATTR: is_superuser_attr: "is_superuser" is_superuser_value: "true"
|
|
6.2. Authentication type: LDAP Copy linkLink copied to clipboard!
General settings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
|
|
Mappings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
AUTH_LDAP_ORGANIZATION_MAP: "LDAP Organization": users: true admins: - "cn=awx_org_admins,ou=groups,dc=example,dc=org"
|
|
AUTH_LDAP_USER_FLAGS_BY_GROUP: is_superuser: - 'cn=awx_admins,ou=groups,dc=example,dc=org'
|
|
6.3. Authentication type: SAML Copy linkLink copied to clipboard!
General settings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
|
|
Mappings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
SOCIAL_AUTH_SAML_ORGANIZATION_MAP: "Default": users: true
|
|
SOCIAL_AUTH_SAML_USER_FLAGS_BY_ATTR: is_superuser_attr: "is_superuser" is_superuser_value: "true"
|
|
6.4. Authentication type: Github Copy linkLink copied to clipboard!
General settings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
SOCIAL_AUTH_GITHUB_KEY: client-id SOCIAL_AUTH_GITHUB_SECRET: client-secret SOCIAL_AUTH_GITHUB_SCOPE: - 'user:email' - 'read:org'
|
|
Mappings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
SOCIAL_AUTH_GITHUB_ORGANIZATION_MAP: "MyOrg": users: true admins: - "admin-team"
|
|
SOCIAL_AUTH_GITHUB_TEAM_MAP: "Developers": organization: "MyOrg" users: - "dev-team"
|
|
6.5. Authentication type: Azure AD Copy linkLink copied to clipboard!
General settings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
SOCIAL_AUTH_AZUREAD_OAUTH2_KEY: "application-id" SOCIAL_AUTH_AZUREAD_OAUTH2_SECRET: "client-secret"
|
"configuration": { "KEY": "application-id", "SECRET": "client-secret", "GROUPS_CLAIM": "groups" }
|
Mappings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
SOCIAL_AUTH_AZUREAD_OAUTH2_ORGANIZATION_MAP: "Azure Organization": users: true
|
|
SOCIAL_AUTH_AZUREAD_OAUTH2_TEAM_MAP: "Admin Team": organization: "Azure Organization" users: - "admin@company.com"
|
|
6.6. Authentication type: RADIUS Copy linkLink copied to clipboard!
General settings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
RADIUS_SERVER: "radius.example.com" RADIUS_PORT: 1812 RADIUS_SECRET: "shared-secret"
|
"configuration": { "SERVER": "radius.example.com", "PORT": 1812, "SECRET": "shared-secret" }
|
Mappings
RADIUS authentication does not support user mappings in either automation controller 2.4 or Platform gateway 2.6.
6.7. Authentication type: TACACS+ Copy linkLink copied to clipboard!
General settings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
|
|
Mappings
TACACS+ authentication does not support user mappings in either automation controller 2.4 or Platform gateway 2.6.
6.8. Authentication type: Google OAuth2 Copy linkLink copied to clipboard!
General settings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
SOCIAL_AUTH_GOOGLE_OAUTH2_KEY: "client-id" SOCIAL_AUTH_GOOGLE_OAUTH2_SECRET: "client-secret" SOCIAL_AUTH_GOOGLE_OAUTH2_SCOPE: ["profile", "email"]
|
|
Mappings
Automation controller 2.4 | Platform gateway 2.6 |
---|---|
SOCIAL_AUTH_GOOGLE_OAUTH2_ORGANIZATION_MAP: "Google Org": users: true
|
|
SOCIAL_AUTH_GOOGLE_OAUTH2_TEAM_MAP: "Engineers": organization: "Google Org" users: true
|
|
6.9. The MANAGE_ORGANIZATION_AUTH setting Copy linkLink copied to clipboard!
The automation controller setting previously called Organization Admins Can Manage Users and Teams in the UI (or MANAGE_ORGANIZATION_AUTH
in the API) controls whether an organization administrator can create users and teams. This setting now exists in both platform gateway and automation controller in Ansible Automation Platform 2.6. During an upgrade the value from automation controller is imported into the platform gateway server. If you decide to change the value of this setting ensure that you change it to the same values in both the platform gateway and automation controller.
For environments with automation running directly against automation controller, maintain a consistent value for MANAGE_ORGANIZATION_AUTH
across both automation controller and platform gateway to avoid unexpected behavior.