Create a third party service with PingAuthorize configured as the target. For more information, see Adding third-party services.

A response filtering rule can modify the response given by PingAccess, based on the response from the PingAuthorize response API.


The PingAuthorize sideband API cannot accept gzipped data from upstream server responses. To prevent the upstream server from sending compressed responses, ensure that upstream server requests add or replace the Accept-Encoding header with Accept-Encoding: identity.

  1. Click Access and then go to Rules > Rules.
  2. Click + Add Rule.
  3. In the Name field, enter a unique name, up to 64 characters long.

    Special characters and spaces are allowed.

  4. From the Type list, select PingAuthorize Response Filtering.
  5. From the Third Party Service list, select your PingAuthorize service.
  6. In the Shared Secret field, enter the shared secret from PingAuthorize.
  7. Optional: To include the HTTP request body in the HTTP request data sent to PingAuthorize, select the Include Request Body check box
  8. Optional: To configure advanced options, click Show Advanced.
    1. Optional: In the Sideband Endpoint field, enter the sideband API endpoint location.
    2. Optional: In the Shared secret header name field, enter a header in which to send the shared secret.
  9. Click Save.