providers/oauth2: add logout+jwt token type for oidc logout token.#19554
Merged
BeryJu merged 2 commits intogoauthentik:mainfrom Jan 22, 2026
Merged
Conversation
The oidc back-channel logout spec recommends using explicitly typed JWTs using the `typ` parameter in the JWT's header. [spec](https://openid.net/specs/openid-connect-backchannel-1_0.html#CrossJWT) This may be a breaking change for some implementations if they were already checking the type of the token to be `JWT` (the default value).
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #19554 +/- ##
==========================================
+ Coverage 92.49% 93.22% +0.73%
==========================================
Files 949 949
Lines 52052 52142 +90
==========================================
+ Hits 48144 48609 +465
+ Misses 3908 3533 -375
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
BeryJu
reviewed
Jan 22, 2026
Signed-off-by: Jens L. <jens@beryju.org>
BeryJu
approved these changes
Jan 22, 2026
✅ Deploy Preview for authentik-storybook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-integrations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
authentik-automation bot
pushed a commit
that referenced
this pull request
Jan 22, 2026
…19554) * providers/oauth2: add `logout+jwt` token type for oidc logout token. The oidc back-channel logout spec recommends using explicitly typed JWTs using the `typ` parameter in the JWT's header. [spec](https://openid.net/specs/openid-connect-backchannel-1_0.html#CrossJWT) This may be a breaking change for some implementations if they were already checking the type of the token to be `JWT` (the default value). * Apply suggestion from @BeryJu Signed-off-by: Jens L. <jens@beryju.org> --------- Signed-off-by: Jens L. <jens@beryju.org> Co-authored-by: Jens L. <jens@beryju.org>
Contributor
|
🍒 Cherry-pick to |
authentik-automation bot
pushed a commit
that referenced
this pull request
Jan 22, 2026
…19554) * providers/oauth2: add `logout+jwt` token type for oidc logout token. The oidc back-channel logout spec recommends using explicitly typed JWTs using the `typ` parameter in the JWT's header. [spec](https://openid.net/specs/openid-connect-backchannel-1_0.html#CrossJWT) This may be a breaking change for some implementations if they were already checking the type of the token to be `JWT` (the default value). * Apply suggestion from @BeryJu Signed-off-by: Jens L. <jens@beryju.org> --------- Signed-off-by: Jens L. <jens@beryju.org> Co-authored-by: Jens L. <jens@beryju.org>
Contributor
|
🍒 Cherry-pick to |
BeryJu
added a commit
that referenced
this pull request
Jan 22, 2026
…(cherry-pick #19554 to version-2025.12) (#19675) providers/oauth2: add `logout+jwt` token type for oidc logout token. (#19554) * providers/oauth2: add `logout+jwt` token type for oidc logout token. The oidc back-channel logout spec recommends using explicitly typed JWTs using the `typ` parameter in the JWT's header. [spec](https://openid.net/specs/openid-connect-backchannel-1_0.html#CrossJWT) This may be a breaking change for some implementations if they were already checking the type of the token to be `JWT` (the default value). * Apply suggestion from @BeryJu --------- Signed-off-by: Jens L. <jens@beryju.org> Co-authored-by: Jeroen <jeroen@velzen.cc> Co-authored-by: Jens L. <jens@beryju.org>
BeryJu
added a commit
that referenced
this pull request
Jan 22, 2026
…(cherry-pick #19554 to version-2025.10) (#19674) providers/oauth2: add `logout+jwt` token type for oidc logout token. (#19554) * providers/oauth2: add `logout+jwt` token type for oidc logout token. The oidc back-channel logout spec recommends using explicitly typed JWTs using the `typ` parameter in the JWT's header. [spec](https://openid.net/specs/openid-connect-backchannel-1_0.html#CrossJWT) This may be a breaking change for some implementations if they were already checking the type of the token to be `JWT` (the default value). * Apply suggestion from @BeryJu --------- Signed-off-by: Jens L. <jens@beryju.org> Co-authored-by: Jeroen <jeroen@velzen.cc> Co-authored-by: Jens L. <jens@beryju.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Details
The oidc back-channel logout spec recommends using explicitly typed JWTs using the
typparameter in the JWT's header.spec
This may be a breaking change for some implementations if they were already checking the type of the token to be
JWT(the default value).Checklist
ak test authentik/)make lint-fix)If an API change has been made
make gen-build)If changes to the frontend have been made
make web)If applicable
make docs)