PingOne

Publishing a policy and configuring an endpoint

Learn how to publish a policy to a decision endpoint and configure the endpoint.

Publishing a policy

About this task

Let’s publish your changes to a decision endpoint so that you can make decision requests against a specific version of the policy. PingOne Authorize provides three decision endpoints to get you started: Dev, Test, and Prod. You’ve been working with the Dev endpoint so far.

Let’s publish to the Test endpoint to make your new policy available for more rigorous testing.

Ensure that your policies and Trust Framework definitions are thoroughly tested before you publish them to the Prod endpoint and use them in production.

Steps

  1. Go to Authorization > Version History.

    You see all the changes you’ve made, with the most recent changes listed first. The orange Dev icon indicates that you’ve been working with the development endpoint.

    Screen capture of Version History showing updates made to the latest versions published to the Dev endpoint.

    Let’s publish the latest version of your changes.

  2. Click the More Options (⋮) icon to the right of (Latest Version) Dev and select Publish Version.

    Screen capture showing selection of Publish Version from the More Options (vertical ellipsis) menu.

  3. In the Publish to list, select the Test endpoint.

  4. For the version Name, enter Payment checks.

  5. Click Publish.

    Result:

    The version is now named and the pink Test icon indicates that it’s published in Test in addition to Dev.

    Screen capture of the named version Payment checks published to the Dev and Test endpoints.

Setting up decision endpoints

About this task

Let’s take a look at the Test endpoint and set it up to record recent decisions.

You can configure a decision endpoint to keep track of recent decisions made during policy evaluation. This can cause a slower system response, so the setting is disabled by default. During policy development, enable this setting as a debugging tool to help you visualize and examine recent decisions.

Steps

  1. Go to Authorization > Decision Endpoints.

  2. Expand the Test endpoint and click the Pencil icon.

    Screen capture of the expanded Test endpoint in Decision Endpoints.

    Result:

    The Editing window opens, and you can see that the endpoint is using the policy version that you published to it.

    Screen capture of editing options for the Test endpoint in Decision Endpoints.

    If you’re wondering about Use latest, this setting allows you to use the latest policy version instead of a specific named version. This republishes the latest version each time a request is made to the endpoint and can cause a slower system response. Don’t enable this setting right now.

  3. Select the Record recent decisions check box.

    When decision requests are made against your policy, this option keeps track of the last 20 decisions and allows you to examine those decisions in detail.

  4. Click Save.

Next steps

You’ve published your policy to an endpoint where it can be tested and you’ve set up the Test endpoint to keep track of recent decisions.

Next, you’ll make decision requests against your policy.