Confirm that you are not using the agent model. Rewrite cookie path rules aren't available for agent deployments.

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/.

To add a rewrite cookie path rule:

  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.

    Special characters and spaces are allowed.

  4. In 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 that you want to display in the response from PingAccess.
  7. Click Save.