> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/key-features/cookie-lifetime-extender/manually-verify-your-cle-configuration.md).

# Manually verify your CLE configuration

We are already working on improving the debugging capabilities of the Cookie Lifetime Extender verification. Until improved error messaging is implemented, please find a guide on manually checking the status of the verification and possible reasons here.

## Installing Postman CLI

For the manual verification check to be working, you need to install the official Postman CLI. You can find the guide [here](https://learning.postman.com/docs/postman-cli/postman-cli-installation/).

## Sending the Postman request

Copy/Paste the codeblock below, replacing "\<yourwebsitedomain> and \<hash> with the values from your DCP CLE settings page.

```
postman request POST 'https://<youwebsitedomain>/<hash>' \
  --header 'Content-Type: application/json' \
  --header 'Cookie: jts-rw={"u":"91409167904637152936318"}' \
  --body '{
    "client": {
        "clientTimestamp": 1743756071564,
        "domain": ".<yourwebsitedomain>"
    },
    "cmd": {
        "key": "setcookie-itp-proxy",
        "data": [
            {
                "name": "jts-rw",
                "value": "{\"u\":\"91409167904637152936318\"}",
                "exdays": 17280000
            }
        ]
    }
}'
```

## Interpreting the response

The responses to this request will be HTTP Response codes

| Response Code                                                                                                                                                                                                                                                                        | Meaning                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- |
| <p>200<br><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FQte0SPQqQuaCMBweA7lH%2FScreenshot%202026-01-28%20at%2012.53.11.png?alt=media&amp;token=fd9ce50d-242d-4a6f-9ebd-906bf481eca9" alt=""></p> | The redirect worked, cookies were set with correct duration! You successfully configured the CLE. :tada:  |
| <p>404<br><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FJHSQgcDuWVCc8i5Lq50Y%2FScreenshot%202026-01-28%20at%2012.58.30.png?alt=media&amp;token=cad57d0e-e9b4-4ee3-8a65-9e137debf0f2" alt=""></p> | The redirect is not working and the request is ending up on a page that is giving back "404 - Not found". |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/key-features/cookie-lifetime-extender/manually-verify-your-cle-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.