Skip to content
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

Update How Clerk works #1811

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Update How Clerk works #1811

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c13ba2d
fix session cookie comprehension check
alexisintech Dec 16, 2024
4cf23ba
simple update to jwt section heading
alexisintech Dec 16, 2024
c593ca8
update session cooke comp check again
alexisintech Dec 16, 2024
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
4 changes: 3 additions & 1 deletion docs/how-clerk-works/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,9 @@ This example assumes that the user already signed up and their credentials are s
>
> ---
>
> This is a great test of your mastery of [how cookies work](/docs/how-clerk-works/cookies)! For security reasons, the domain of a cookie can only be set as the domain of the server that set the cookie. The server that is returning the request to your application is FAPI. For the client cookie, this is ok, since the client cookie is set on FAPI. However, FAPI cannot set a cookie with your app's domain because it's not your app. Remember, if your app is running at `example.com`, FAPI would run at `clerk.example.com`. Instead, FAPI it sends back the **JWT value** of the session cookie in its response, and Clerk's client side SDK picks it up and uses javascript to set the session cookie on your app directly, since the javascript is running on your app's domain.
> This is a great test of your mastery of [how cookies work](/docs/how-clerk-works/cookies)!
>
> The server that is returning the request to your application is FAPI. For the **client cookie**, this is ok, since the **client cookie** needs to be set on FAPI. However, the **session cookie** needs to be set on your app's domain and remember, **the domain of a cookie can only be set as the domain of the server that set the cookie**. So FAPI cannot set the domain of your **session cookie** to your app's domain. Instead, FAPI returns the **JWT value** of the session cookie in its response, and when the Clerk client-side SDK integrated in your app receives the response, it gets the **JWT value** and uses JavaScript to set the **session cookie** on your app directly, since the JavaScript is running on your app's domain.

<Video
src="/docs/images/how-clerk-works/hybrid-auth.mp4"
Expand Down
2 changes: 1 addition & 1 deletion docs/how-clerk-works/tokens-signatures.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ So for example, imagine you get a publicly readable message, like `hello world`,

Clerk leverages digital signatures in **JSON Web Tokens (JWTs)** to securely authenticate users.

## JWTs
## JSON Web Tokens (JWTs)

JSON Web Tokens (JWTs) are a lightweight format for transmitting digitally signed data over the internet. They are commonly used for authentication and information exchange.

Expand Down
Loading