PingOne

Authorize gateway version history

This page provides details about Authorize gateway versions, including release dates, a summary of features and known limitations, and critical end-of-support information for each version.

Learn more about gateway support policies in Authorize gateway support lifecycle.

You can find information about upgrading gateway versions in Upgrading an Authorize gateway instance.

Version 1.1.0

Milestone Date

Release

August 27, 2025

Highlights

Policy authoring

Authorize gateways now support:

  • The Is Member Of and Is Not Member Of condition comparators in policies and rules

  • User attributes listed under PingOne on the Attributes tab

  • The PingOne User and PingOne User ID resolvers in attributes

Administrator permissions

  • The new Authorize Gateway Policy Evaluator built-in role is automatically assigned to Authorize gateways. This role provides least-privilege permissions for reading Authorize gateways and authorization deployments.

  • To grant an Authorize gateway additional policy evaluation permissions, such as reading user details, checking group membership, and evaluating risk scores, create a custom role on the new Roles tab.

Learn more about built-in and custom roles in Managing Authorize gateway roles.

Logging

  • Authorize gateways now log all service calls made to PingOne. You can use entries in the PINGONE_SERVICE_AUDIT log to monitor and troubleshoot policy interactions with PingOne, such as user attribute resolution and group membership checks.

  • As in the previous version, logs are omitted when they include sensitive terms. You can set logging.allowSensitiveMaterial:true to disable log filtering.

Learn more in Logging for Authorize gateway instances.

Additional enhancements

Limitations

The following features aren’t supported for Authorize gateway deployments:

  • Calls to gateway instances from the PingOne Authorize DaVinci connector.

  • API Access Management in PingOne Authorize.

  • The Authorization Dashboard doesn’t track metrics for decision evaluations made by gateway instances.

Policies

The following policy features aren’t supported:

  • The Has Permissions condition comparator in policies and rules

  • Attributes listed under PingOne > API Access Management on the Attributes tab

Policy features that rely on PingOne might increase decision request latency. These include:

  • PingOne User and PingOne User ID attribute resolvers

  • Is Member Of and Is Not Member Of condition comparators

  • PingOne Protect Connector services that provide risk information to gateway instances

If your policies include these features, you must assign a built-in or custom administrator role to the Authorize gateway to give it additional permissions in PingOne. Learn more in Managing Authorize gateway roles.

Information points

The following features aren’t supported:

  • You can’t use an LDAP Gateway service to access user information stored in an on-premise LDAP directory.

  • When testing services, you can’t test calls to your local or private services. However, you can use overrides to mock the service response.

Version 1.0.0

Milestone Date

Release

January 20, 2025

End of support

February 28, 2026

End of life

February 28, 2027

Support notification

August 27, 2025

Highlights

Version 1.0.0 is the first Authorize gateway release.

To reduce authorization latency, you can deploy authorization policies managed in PingOne to Authorize gateway instances located on-premise or in your private cloud. In highly regulated environments, this ensures data privacy by keeping sensitive data for authorization decisions within your secure trust boundary.

Limitations

The following features aren’t supported in version 1.0.0:

  • Calls to gateway instances from the PingOne Authorize DaVinci connector.

  • API Access Management in PingOne Authorize.

  • The Authorization Dashboard doesn’t track metrics for decision evaluations made by gateway instances.

Policies

You can use many of the policy authoring features available in PingOne Authorize. However, the following features aren’t supported in version 1.0.0:

  • The Has Permissions, Is Member Of, and Is Not Member Of condition comparators in policies and rules

  • Attributes listed under PingOne on the Attributes tab, including User and API Access Management attributes

  • The PingOne User and PingOne User ID resolvers in attributes

Information points

You can make calls to information points and on-premise services directly from gateway instances. When you set up an HTTP service in PingOne, use URLs for your local or private services instead of public URLs.

The following features aren’t supported:

  • You can’t use an LDAP Gateway service to access user information stored in an on-premise LDAP directory.

  • You can’t use a Connector service to provide risk information to gateway instances.

  • When testing services, you can’t test calls to your local or private services. However, you can use overrides to mock the service response.