PingAccess

Adding rewrite cookie path rules

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 PingAccess to manage the details of exposed applications 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/.

Before you begin

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

Steps

  1. Click Access, 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.