Validating gateway authentication after the 2.7 upgrade

After upgrading to Red Hat Ansible Automation Platform 2.7, validate that all platform components and integrations are functioning correctly with gateway-based authentication.

About this task

Validation checklist

Confirm the following results to ensure the upgrade was successful:

  • Users can log in to the platform gateway UI.
  • Direct access to component APIs (controller, hub, or EDA) returns an HTTP 401 Unauthorized response.
  • Job templates launch successfully through the platform gateway API.
  • Collections download from automation hub through the gateway.
  • Container registry authentication works using podman login or docker login.
  • Event-Driven Ansible rulebook activations are in a Running state.
  • Configuration as Code (CaC) playbooks execute successfully.
  • Third-party authentication providers, such as LDAP or SAML, function through the gateway.

Procedure

Quick validation commands
  1. Test platform gateway API access: 
    $ curl -H "Authorization: Bearer ${GATEWAY_TOKEN}" \
  https://gateway.example.com/api/gateway/v1/ping/
  2. Verify direct access is blocked (should return 401): 
    $ curl -H "Authorization: Bearer ${OLD_TOKEN}" \
  https://controller.example.com/api/v2/ping/

Results

In Ansible Automation Platform 2.7, authentication at the component level is disabled for external requests. An HTTP 401 Unauthorized response for direct component access is the correct behavior.

What to do next

If validation steps fail, see the following resources: