IT Automation
REMOTE_USER / X-Forwarded-User
Zero-Day Shield

SSO + Zero-Day Protection for AWX / Ansible Automation Platform

by Red Hat (Ansible)

Add SAML/OIDC SSO to AWX — Shield Ansible Automation from Zero-Day Exploits

Why AWX / Ansible Automation Platform Needs an Authenticated Proxy

AWX is the open-source upstream project for Red Hat Ansible Automation Platform, providing a web UI, REST API, and job engine for running Ansible playbooks. AWX manages machine credentials (SSH keys, passwords, cloud API tokens), playbook inventories, and job templates that execute with privileged access across your infrastructure. A compromised AWX instance gives attackers the ability to execute arbitrary Ansible playbooks on any managed host, extract stored credentials, and modify infrastructure configuration at scale. OnePAM adds enterprise SSO and zero-day protection by placing an authenticated reverse proxy in front of AWX. Users authenticate via your corporate IdP, and OnePAM ensures only verified users can access automation resources.

HTTP Header Authentication
REMOTE_USER / X-Forwarded-User

AWX supports external authentication via a trusted proxy that provides the authenticated username. OnePAM injects the verified identity header, and AWX creates the session based on the trusted user.

AWX / Ansible Automation Platform Vulnerability Risks

Without an authenticated proxy, these risks are directly exploitable by any network-reachable attacker.

AWX/Tower has had critical RCE vulnerabilities via playbook injection
Machine credentials (SSH keys, cloud API tokens) are stored in AWX credential vault
Playbook execution provides root-level access to all managed infrastructure
Inventory data reveals complete infrastructure topology and access patterns

Security Challenges with AWX / Ansible Automation Platform

These are the risks organizations face when AWX / Ansible Automation Platform is not behind an authenticated proxy.

Infrastructure-Wide Access

AWX playbooks execute with privileged access across all managed hosts. Unauthorized execution enables infrastructure-wide compromise.

Credential Vault Exposure

AWX stores SSH keys, passwords, cloud API tokens, and vault passwords needed by playbooks. Compromise exposes all managed credentials.

Playbook Injection Risk

AWX has had vulnerabilities allowing malicious playbook injection, enabling arbitrary code execution on managed hosts.

Inventory Data Sensitivity

AWX inventories document every managed host, group, and variable — a complete map of your automation-managed infrastructure.

Limited OSS Auth

AWX (open source) has more limited authentication options compared to the commercial Ansible Automation Platform.

Job Template Manipulation

Unauthorized job template modification can change which playbooks run, with what credentials, on which hosts.

How OnePAM Adds SSO + Zero-Day Protection to AWX / Ansible Automation Platform

A step-by-step guide to deploying OnePAM's authenticated proxy in front of AWX / Ansible Automation Platform.

1

Deploy OnePAM as AWX's Gateway

Place OnePAM in front of the AWX web interface and API.

AWX's NGINX is configured to accept connections only from OnePAM. The AWX login page is never directly accessible.
2

Configure IdP Federation

Connect OnePAM to your corporate IdP — Okta, Azure AD, Google Workspace, or any SAML/OIDC provider.

OnePAM handles authentication, MFA enforcement, and group membership retrieval.
3

Enable Proxy Authentication

OnePAM injects the authenticated user identity via HTTP headers that AWX trusts.

AWX accepts the pre-authenticated identity and creates user sessions automatically. No AWX login page is shown.
4

Map Automation Access

IdP groups determine who can access which organizations, inventories, and job templates.

Platform engineers get admin access, operators execute pre-defined templates, and auditors get read-only views — from your IdP.
5

Audit Automation Operations

Every AWX operation is logged with corporate identity context.

Know who launched which playbook, on which hosts, with what credentials, and what the results were.

Benefits of Securing AWX / Ansible Automation Platform with OnePAM

Measurable security and operational outcomes from deploying OnePAM in front of AWX / Ansible Automation Platform.

Protect Automation Infrastructure

Only authenticated users can access AWX. Playbook injection and RCE CVEs are blocked at the proxy layer.

Zero unauthorized automation access

Shield Machine Credentials

SSH keys, cloud API tokens, and vault passwords are protected behind identity-verified access.

Credential theft prevented

Enterprise SSO for AWX

OnePAM provides SAML/OIDC SSO for AWX without requiring Ansible Automation Platform licensing.

Enterprise SSO at no extra cost

MFA for Automation

Require MFA before launching playbooks or accessing credential vaults.

MFA-gated automation

Identity-Tied Job Execution

Every playbook execution is linked to a verified corporate identity.

Identity-bound automation

Complete Automation Audit

Every job launch, credential access, and inventory change is logged with corporate identity.

Full automation audit trail

AWX / Ansible Automation Platform SSO Capabilities

Every feature needed to provide enterprise-grade SSO and access control for AWX / Ansible Automation Platform.

SAML 2.0 & OIDC SSO for AWX via proxy authentication
Organization and team access policies from IdP groups
Job template execution authorization
Credential vault access controls
Session recording for automation operations
IP and geo-restriction for AWX access
Device trust verification
REST API access policies and auditing
Inventory access controls
Multi-AWX instance SSO support

Zero-Day Protection Features

Enterprise-grade security controls that shield AWX / Ansible Automation Platform from exploitation.

AWX isolated from direct network access
End-to-end TLS encryption
Request-level identity verification
Protection against AWX playbook injection CVEs
Credential vault access auditing
Automatic session termination on IdP sign-out

AWX / Ansible Automation Platform SSO + Security Use Cases

Common scenarios where organizations deploy OnePAM in front of AWX / Ansible Automation Platform.

1
Platform engineers managing Ansible automation via corporate SSO with MFA
2
Operators executing pre-defined job templates with restricted access
3
Security teams auditing automation operations with session recording
4
Restricting production playbook execution to senior engineers with step-up MFA
5
Protecting AWX from playbook injection and RCE exploitation
6
Compliance-driven automation access auditing for SOC 2 and PCI DSS

AWX / Ansible Automation Platform SSO + Security FAQ

Common questions about deploying OnePAM's authenticated proxy for AWX / Ansible Automation Platform.

Does OnePAM work with AWX (open source) or only Ansible Automation Platform?

OnePAM works with both AWX (open source) and Red Hat Ansible Automation Platform. Proxy authentication is supported in both editions.

Can we restrict who can launch specific job templates?

Yes. OnePAM passes IdP group memberships that map to AWX organizations and teams. AWX's RBAC system controls which teams can access and execute specific job templates.

Does OnePAM protect the AWX REST API?

Yes. OnePAM enforces authentication on all AWX endpoints. Automated API calls can use tokens while interactive sessions require full SSO.

Can we require MFA for production playbook execution?

Yes. OnePAM supports path-based and context-aware policies. Production job launches can require step-up MFA while read-only access uses standard SSO.

Does OnePAM affect AWX callback and webhook endpoints?

OnePAM supports policy exceptions for specific endpoints. AWX callback URLs and webhook receivers can be configured with different authentication requirements.

Ready to Secure AWX / Ansible Automation Platform with SSO + Zero-Day Protection?

Deploy OnePAM in minutes — no AWX / Ansible Automation Platform code changes required. Start your free 14-day trial today.