--- title: Authorize gateway version history description: History of Authorize gateway versions, including release dates, highlights, limitations, and end of support information. component: pingone page_id: pingone:integrations:p1_authz_gateway_version_history canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_authz_gateway_version_history.html revdate: May 15, 2026 keywords: ["version history", "authorize gateway", "limitations", "support"] section_ids: version-1-2-1: Version 1.2.1 highlights: Highlights security-updates: Security updates gateway-instance-startup-message: Gateway instance startup message structured-errors-for-invalid-decision-requests: Structured errors for invalid decision requests limitations: Limitations policies: Policies information-points: Information points version-1-2-0: Version 1.2.0 highlights-2: Highlights bulk-decision-requests: Bulk decision requests enhanced-logging: Enhanced logging limitations-2: Limitations policies-2: Policies information-points-2: Information points version-1-1-0: Version 1.1.0 highlights-3: Highlights policy-authoring: Policy authoring administrator-permissions: Administrator permissions logging: Logging additional-enhancements: Additional enhancements limitations-3: Limitations policies-3: Policies information-points-3: Information points version-1-0-0: Version 1.0.0 highlights-4: Highlights limitations-4: Limitations policies-4: Policies information-points-4: Information points --- # 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](p1_authz_gateway_support_lifecycle.html). You can find information about upgrading gateway versions in [Upgrading an Authorize gateway instance](p1_upgrade_authz_gateway_instance.html). ## Version 1.2.1 | Milestone | Date | | --------- | ------------ | | Release | May 21, 2026 | ### Highlights #### Security updates We've updated underlying runtime components to address potential security vulnerabilities in the HTTP network stack and Docker base image. #### Gateway instance startup message To help manage Authorize gateways across multiple environments, gateway instances now log identifying information on startup for the associated gateway and PingOne environment. Learn more in [Startup logging](p1_logging_authz_gateway_instances.html#p1_az_gateway_startup_logging). #### Structured errors for invalid decision requests Gateway instances now return structured, field-level error responses for invalid `userContext` values in decision requests. Previously, such requests returned a generic error message without identifying the specific field or validation failure. ### 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. #### Information points The following features aren't supported: * You can't use an **LDAP Gateway** service to access user information stored in a self-managed LDAP directory. * When [testing services](../authorization_using_pingone_authorize/p1_az_testing_tf_elements.html), you can't test calls to your local or private services. However, you can use overrides to mock the service response. ## Version 1.2.0 | Milestone | Date | | -------------------- | ------------------ | | Release | September 30, 2025 | | End of support | May 31, 2027 | | Support notification | May 21, 2026 | ### Highlights #### Bulk decision requests Authorize gateway instances now support bulk decision requests, allowing you to evaluate multiple access scenarios with a single API call. Bulk requests reduce both network overhead and overall decision latency, improving performance in high-throughput environments. Learn more in [Making decision requests to Authorize gateway instances](p1_make_decision_requests_to_authz_gateway_instances.html). #### Enhanced logging When you start a gateway instance that doesn't support features in the authorization policy version published to the gateway, the system now logs a detailed error message. This message explains that the instance can't retrieve the PingOne configuration and directs you to upgrade to a supported version. Learn more in [Logging for Authorize gateway instances](p1_logging_authz_gateway_instances.html). ### 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. #### Information points The following features aren't supported: * You can't use an **LDAP Gateway** service to access user information stored in a self-managed LDAP directory. * When [testing services](../authorization_using_pingone_authorize/p1_az_testing_tf_elements.html), you can't test calls to your local or private services. However, you can use overrides to mock the service response. ## Version 1.1.0 | Milestone | Date | | -------------------- | ------------------ | | Release | August 27, 2025 | | End of support | October 31, 2026 | | Support notification | September 30, 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](p1_manage_authz_gateway_roles.html). #### 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](p1_logging_authz_gateway_instances.html). #### Additional enhancements * You can now use a **Connector** type service to provide risk signals to gateway instances. Learn more in [Connecting to PingOne Protect](../authorization_using_pingone_authorize/p1_az_connecting_p1_risk.html). * Service caching TTLs and timeouts for PingOne calls are now configurable. Learn more in [Service caching and timeouts for Authorize gateway instances](p1_service_caching_authz_gateway_instances.html). ### 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](p1_manage_authz_gateway_roles.html). #### Information points The following features aren't supported: * You can't use an **LDAP Gateway** service to access user information stored in a self-managed LDAP directory. * When [testing services](../authorization_using_pingone_authorize/p1_az_testing_tf_elements.html), 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 | August 31, 2026 | | 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 self-managed services directly from gateway instances. When you [set up an HTTP service](../authorization_using_pingone_authorize/p1_az_connecting_an_http_service.html) 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 a self-managed LDAP directory. * You can't use a **Connector** service to provide risk information to gateway instances. * When [testing services](../authorization_using_pingone_authorize/p1_az_testing_tf_elements.html), you can't test calls to your local or private services. However, you can use overrides to mock the service response.