Testing the policy from the Policy Editor - PingAuthorize - 9.2

PingAuthorize

bundle
pingauthorize-92
ft:publication_title
PingAuthorize
Product_Version_ce
PingAuthorize 9.2
category
ContentType
Product
Productdocumentation
paz-92
pingauthorize
ContentType_ce
Product documentation

We can now test the policy and make sure that it works as we intend. First, we test the policy directly from the Policy Editor's test interface.

  1. In the Policy Editor, click the Test tab at the top of the main pane to display the test interface.
  2. Fill out the Request section. The test uses this information to simulate the policy request that PingAuthorize Server makes when it receives an HTTP request.
    Description Details

    Service

    Meme Games - Games

    Action

    inbound-POST

    Attributes

    HttpRequest.AccessToken

    { "active": true, "sub": "user.99@example.com" }

    The following image shows the test.


    Screen capture of the test scenario screen with the Service, Action, and Attributes defined as indicated and the Execute button in the bottom right
  3. Click Execute.

    The policy test result displays. If the policy worked as expected, the leftmost result is red, indicating a DENY result.


    Screen capture of the Visualization screen on the Test Results tab displaying a deny decision flow triggered by the deny condition
  4. Optional: Experiment with testing.

    Click the Testing Scenario tab and try different inputs to see how the policy result changes. For example, change the HttpRequest.AccessToken attribute value to { "active": true, "sub": "user.99@my-company.com" }. The policy result is now PERMIT, as shown in the following image.


    Screen capture of the Visualization screen on the Test Results tab displaying a permit decision flow from a not applicable result for the deny condition