---
title: Adding rewrite cookie domain rules
description: Add a rewrite cookie domain rule, which converts the cookie domain returned by the site into a public-facing domain, in PingAccess.
component: pingaccess
version: 8.3
page_id: pingaccess:pingaccess_user_interface_reference_guide:pa_adding_rewrite_cookie_domain_rules
canonical_url: https://docs.pingidentity.com/pingaccess/9.1/pingaccess_user_interface_reference_guide/pa_adding_rewrite_cookie_domain_rules.html
llms_txt: https://docs.pingidentity.com/pingaccess/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: January 12, 2024
superseded_by: https://docs.pingidentity.com/pingaccess/9.1/pingaccess_user_interface_reference_guide/pa_adding_rewrite_cookie_domain_rules.html
section_ids:
  before-you-begin: Before you begin
  about-this-task: About this task
  steps: Steps
---

# 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](../introduction_to_pingaccess/pa_agent_model.html) 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, `myserver.acme.com` can be set to `acme.com`. |

To add a rewrite cookie domain rule:

## Steps

1. Click **Access**, then go to **Rules > Rules**.

2. Click **[icon: plus, set=fa]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 Domain**.

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

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

7. In the **Public-Facing Cookie Domain** field, enter the domain name that you want to display in the response from PingAccess.

8. Click **Save**.