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.

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

chore: clarify jwt tokenizer #1970

Merged
merged 3 commits into from
Dec 20, 2024
Merged
Changes from 1 commit
Commits
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
7 changes: 4 additions & 3 deletions docs/identities/session-to-jwt-cors.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,11 @@ sidebar_label: Session to JWT

# Convert Ory Sessions to JSON Web Tokens

Ory offers a powerful session management system that is based on cookies. In some contexts however, relying on Cookies is not
possible:
Ory offers a powerful session management system that is based on Ory Session Cookies for browser clients and Ory Session Tokens
vinckr marked this conversation as resolved.
Show resolved Hide resolved
for API clients. In some contexts it is a better option to use a JSON Web Token:
vinckr marked this conversation as resolved.
Show resolved Hide resolved

- You need to make a cross-origin (CORS) request where including the Ory Session Cookie is not trivial or possible.
- You need to make a cross-origin (CORS) request where including the Ory Session Cookie or Ory Session Token is not trivial or
possible.
- You need a JWT which represents a signed-in user.
- You need to integrate with a third party such as
[Zendesk SSO JWTs](https://support.zendesk.com/hc/en-us/articles/4408845838874).
Expand Down
Loading