Requirements for Authorize gateways

The administrator setting up Authorize gateways must have the Environment Admin role in PingOne. This grants the Read Authorize Gateway Deployment permission required for working with Authorize gateways.

Authorize gateways have the Authorize Gateway Policy Evaluator role by default. This role grants the minimum permissions required for Authorize gateways to interact with PingOne. If an Authorize gateway requires additional permissions, grant additional roles to the gateway. Learn more in Managing Authorize gateway roles.

Make sure the PingOne environment that you’re using for self-managed deployments includes the PingOne SSO and PingOne Authorize services.

Learn more about setting up environments in Creating an environment.

To run a containerized Authorize gateway instance, you must have Docker installed on the machine that will run the gateway instance.

The Docker environment that will run the Authorize gateway instance must have the following resources dedicated to the gateway instance:

The Authorize gateway instance requires the ability to initiate outbound requests over the internet to establish a WebSocket Secure connection and HTTPS connections to PingOne.

The WebSocket Secure address varies depending on your region. Ensure that the gateway instance can access the WebSocket Secure address for your region: