Adding rewrite cookie domain rules
Add a rewrite cookie domain rule, which converts the cookie domain returned by the site into a public-facing domain, in PingAccess.
Before you begin
Confirm that you are not using the agent model. Rewrite cookie domain rules aren’t available for agent deployments.
About this task
When a site places a cookie on a cookie domain such as internalsite.com, or .internalsite.com, PingAccess rewrites the Domain portion of the Set-Cookie response header with a public-facing domain such as publicsite.com, or .publicsite.com, using the information configured in the rewrite cookie domain rule.
|
You should only set the cookie in the Public-Facing Cookie Domain field to the virtual host name associated with that application, or to a domain that is above. For example, |
To add a rewrite cookie domain rule:
Steps
-
Click Access and then go to Rules → Rules.
-
Click Add Rule.
-
In the Name field, enter a unique name up to 64 characters.
Special characters and spaces are allowed.
-
In the Type list, select Rewrite Cookie Domain.
-
If you need to explicitly define the target host, clear the Any Site Target Host check box.
When you select the Any Site Target Host check box, PingAccess will rewrite the cookie domain if it is set to the domain defined in a site’s target host list.
-
If you clear the Any Site Target Host check box, enter the domain name used by the backend site in the Server-Facing Cookie Domain field.
-
In the Public-Facing Cookie Domain field, enter the domain name that you want to display in the response from PingAccess.
-
Click Save.