Skip to content

chore: add jti claim to OIDC docs #86

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
wass3rw3rk merged 2 commits into from
Apr 3, 2026
Merged

chore: add jti claim to OIDC docs #86

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9de32dd
chore: add jti claim to OIDC docs
ecrupper Apr 2, 2026
d3b0686
Merge branch 'main' into chore/jti-claim
ecrupper Apr 3, 2026
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
2 changes: 1 addition & 1 deletion docs/usage/open_id_connect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,7 @@ The `id_request` key being set to _anything_ will result in the injection of the
"exp": 1717699924,
"iat": 1717699624,
"iss": "https://vela-server.com/_services/token",
"jti": "e98eea96-9efb-4071-b794-08b89ef2fa3e",
"aud": [
"artifactory"
],
Expand Down Expand Up @@ -111,4 +112,3 @@ There are many resources on validating OpenID tokens. Some of the high level req
- Can the token be validated using the JWKs located at the well-known path of the issuer?
- Do the claims of the ID token match the cloud service expectations?
- Are the claims all members of the `supported_claims` field located at the well-known OpenID configuration?

Loading