Skip to content

[ZT] Validate Access JWT header instead of cookie #24376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 13, 2025
Merged

[ZT] Validate Access JWT header instead of cookie #24376

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7664b65
use header instead of cookie
ranbel Aug 12, 2025
4ad3ba6
update instructions to use the header
ranbel Aug 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/content/docs/cloudflare-one/identity/authorization-cookie/validating-json.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ sidebar:

import { GlossaryTooltip } from "~/components";

When Cloudflare sends a request to your origin, the request will include an [application token](/cloudflare-one/identity/authorization-cookie/application-token/) as a `Cf-Access-Jwt-Assertion` request header and as a `CF_Authorization` cookie.
When Cloudflare sends a request to your origin, the request will include an [application token](/cloudflare-one/identity/authorization-cookie/application-token/) as a `Cf-Access-Jwt-Assertion` request header. Requests made through a browser will also pass the token as a `CF_Authorization` cookie.

Cloudflare signs the token with a key pair unique to your account. You should validate the token with your public key to ensure that the request came from Access and not a malicious third party.
Cloudflare signs the token with a key pair unique to your account. You should validate the token with your public key to ensure that the request came from Access and not a malicious third party. We recommend validating the `Cf-Access-Jwt-Assertion` header instead of the `CF_Authorization` cookie, since the cookie is not guaranteed to be passed.

## Access signing keys

Expand Down Expand Up @@ -72,7 +72,7 @@ As shown in the example below, `https://<your-team-name>.cloudflareaccess.com/cd

To verify the token manually:

1. Copy the JWT from the `CF_Authorization` cookie or from the `Cf-Access-Jwt-Assertion` request header.
1. Copy the JWT from the `Cf-Access-Jwt-Assertion` request header.

2. Go to [jwt.io](https://jwt.io/).

Expand Down