---
title: Adding rewrite cookie path rules
description: Add a rewrite cookie path rule, which converts the cookie path returned by the site into a public-facing path in PingAccess.
component: pingaccess
version: 9.0
page_id: pingaccess:pingaccess_user_interface_reference_guide:pa_adding_rewrite_cookie_path_rules
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/pingaccess_user_interface_reference_guide/pa_adding_rewrite_cookie_path_rules.html
revdate: October 7, 2025
section_ids:
  before-you-begin: Before you begin
  steps: Steps
---

# 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](../introduction_to_pingaccess/pa_choose_a_deployment_model.html#agent) model. Rewrite cookie path rules aren't available for agent deployments.

## 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 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**.