Adding rewrite cookie path rules - PingAccess - 7.2

PingAccess

bundle
pingaccess-72
ft:publication_title
PingAccess
Product_Version_ce
PingAccess 7.2
category
Product
pa-72
pingaccess
ContentType_ce

Add a rewrite cookie path rule, which converts the cookie path returned by the site into a public-facing path, in PingAccess.

This task enables the details of exposed applications to be managed by PingAccess for security and request routing purposes. For example, a site places a cookie in a server-facing cookie path such as /content/. Using the information configured in the rewrite cookie path rule, PingAccess rewrites the Path portion of the Set-Cookie response header with a public-facing cookie path such as /importantstuff/.

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

    The name can be up to 64 characters long. Special characters and spaces are allowed.

  4. From the Type list, select Rewrite Cookie Path.
  5. In the Server-Facing Cookie Path field, enter the path name where the cookie is valid for the backend site.
  6. In the Public-Facing Cookie Path field, enter the path name you want to display in the response from PingAccess.
  7. Click Save.