From 9de32dd355a24c1ad64f7d8de1aeb2acf12fc806 Mon Sep 17 00:00:00 2001 From: ecrupper Date: Thu, 2 Apr 2026 12:35:34 -0500 Subject: [PATCH] chore: add jti claim to OIDC docs --- docs/usage/open_id_connect.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/usage/open_id_connect.md b/docs/usage/open_id_connect.md index a5c44f7..de6f421 100644 --- a/docs/usage/open_id_connect.md +++ b/docs/usage/open_id_connect.md @@ -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" ], @@ -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? -