--- title: Publishing authorization policy versions to Authorize gateways description: To publish policy and Trust Framework versions to an Authorize gateway, use Version History or edit the gateway. component: pingone page_id: pingone:integrations:p1_publish_policy_versions_to_authz_gateway_instances canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_publish_policy_versions_to_authz_gateway_instances.html section_ids: before-you-begin: Before you begin publish-a-version-in-version-history: Publish a version in Version History steps: Steps result: Result: select-a-version-in-an-authorize-gateway: Select a version in an Authorize gateway steps-2: Steps --- # Publishing authorization policy versions to Authorize gateways To publish policy and Trust Framework versions to an Authorize gateway, use **Version History** or edit the gateway. Publishing a version is like saving a snapshot of your policies and Trust Framework definitions. The published version reflects the state of these objects at a specific point in time. Learn more in [Authorization policy version history](../authorization_using_pingone_authorize/p1az_version_history.html). | | | | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | You can also publish authorization policy versions to cloud-based [decision endpoints](../authorization_using_pingone_authorize/p1az_decision_endpoints.html). However, decision endpoints don't provide the data residency and reduced latency benefits of gateway instances deployed in your organization's infrastructure. | Each gateway instance associated with the same Authorize gateway uses the authorization policy version published to that gateway. Publishing a version to an Authorize gateway downloads and stores the authorization policy version deployment configuration locally in the gateway instances in your infrastructure. | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | | Publishing could fail if policies include features that aren't compatible with gateway instances, such as version differences or unsupported features. Learn more about unsupported features in [Policies published to Authorize gateways](p1_policies_published_to_authz_gateways.html).To take advantage of the latest policy features, [upgrade your gateway instance](p1_upgrade_authz_gateway_instance.html). | ## Before you begin * Build your authorization policies in PingOne. Learn more in [Policies](../authorization_using_pingone_authorize/p1az_policies.html). * [Set up an Authorize gateway](p1_set_up_authz_gateway.html). * [Start an Authorize gateway instance](p1_start_authz_gateway_instance.html). * If your authorization policies include PingOne user details, group membership checks, or risk scores from the PingOne Protect Connector, you must assign built-in or custom administrator roles to the Authorize gateway to give it additional permissions in PingOne. Learn more in [Managing Authorize gateway roles](p1_manage_authz_gateway_roles.html). - Version History - Authorize gateway ## Publish a version in Version History You can use **Version History** to publish authorization policy versions to gateway instances. This method enables you to view which versions are published to particular Authorize gateways. ### Steps 1. In the PingOne admin console, go to **Authorization > Version History**. 2. Click the **More Options** (⋮) icon next to the version you want to publish and select **Publish Version**. ![A screen capture of the Version History page with Publish Version highlighted in the More Options menu.](_images/p1-az-version-history-publish-az-gateway.png) In this example, the **Prod Gateway**, **Test Gateway**, and **Dev Gateway** Authorize gateways were created using the **Bootstrap** authorization policy version. You can also see that the **Prod** and **Test** cloud-based decision endpoints use the **Bootstrap** version, and that the **Dev** decision endpoint uses the latest authorization policy version by default. You'll publish versions to Authorize gateways and not to cloud-based decision endpoints. 3. In the **Publish to** list, select an Authorize gateway. ![A screen capture of the Publish to list with a gateway selected.](_images/p1-az-version-history-publish-select-az-gateway.png) 4. If you're publishing the latest version, which is unnamed, enter a **Name** that makes the version easy to identify. If you're publishing a version that's already named, you can use the existing name or change it. ![A screen capture of the Publish Version page with a gateway selected and the version Name set to 'Payment checks'.](_images/p1-az-version-history-name-az-gateway.png) 5. Click **Publish**. #### Result: The latest version is renamed and it is now published to the **Dev Gateway**, in addition to the **Dev** decision endpoint. ![A screen capture of the Version History page with the Payment checks authorization policy version published to the Dev Gateway and the Dev decision endpoint.](_images/p1-az-version-history-az-gateways.png) ## Select a version in an Authorize gateway This method for publishing authorization policy versions provides a convenient way to change the version when you're editing a gateway. ### Steps 1. In the PingOne admin console, make sure that you've [named an authorization policy version](../authorization_using_pingone_authorize/p1az_naming_versions.html). As an example, you'll use the **Payment checks** version that's published to the **Dev Gateway** and promote it to the **Test Gateway**. 2. Go to **Integrations > Gateways** and click the Authorize gateway you want to work with. 3. On the **Configuration** tab, click **Edit**. 4. Select an **Authorization Version**. ![A screen capture of the Authorization Version page with Payment checks selected as the version to use.](_images/p1-az-gateway-add-version-payment-checks.png) 5. Click **Save**. This updates the authorization policy version that the gateway will download and deploy to any associated gateway instances. ![A screen capture of the gateway's Configuration tab showing the version ID and version name.](_images/p1-az-gateway-configuration-tab-payment-checks.png) **Version History** also reflects which authorization policy version the Authorize gateway is using. ![A screen capture of the Version History page showing the Payment checks authorization policy version published to the Dev endpoint and the Dev and Test gateways.](_images/p1-az-version-history-az-gateways-published.png)