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
- Click Access and then go to .
- Click + Add Rule.
In the Name field, enter a unique name.
The name can be up to 64 characters long. Special characters and spaces are allowed.
- From the Type list, select Rewrite Cookie Path.
- In the Server-Facing Cookie Path field, enter the path name where the cookie is valid for the backend site.
- In the Public-Facing Cookie Path field, enter the path name you want to display in the response from PingAccess.
- Click Save.