providers/oauth2: allow cross-provider token introspection#19867
Open
harryyoud wants to merge 1 commit intogoauthentik:mainfrom
Open
providers/oauth2: allow cross-provider token introspection#19867harryyoud wants to merge 1 commit intogoauthentik:mainfrom
harryyoud wants to merge 1 commit intogoauthentik:mainfrom
Conversation
✅ Deploy Preview for authentik-integrations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-storybook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
harryyoud
commented
Jan 29, 2026
| refresh_token = RefreshToken.objects.filter(token=raw_token, provider__in=providers).first() | ||
| if refresh_token: | ||
| return TokenIntrospectionParams(refresh_token, provider) | ||
| return TokenIntrospectionParams(refresh_token, refresh_token.provider) |
Author
There was a problem hiding this comment.
Please may I have some advice on whether we should be returning the authenticated provider or the original token's provider in the introspection response - this only influences the client_id part of the token JSON response
harryyoud
commented
Jan 29, 2026
| if access_token: | ||
| return TokenIntrospectionParams(access_token, provider) | ||
| refresh_token = RefreshToken.objects.filter(token=raw_token, provider=provider).first() | ||
| return TokenIntrospectionParams(access_token, access_token.provider) |
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Author
|
Tested; working well for me. I've published a testing server docker image at https://github.com/harryyoud/authentik/pkgs/container/authentik with these changes. |
Author
|
@BeryJu are you happy to review this since you commented: #11597 (comment) |
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
1 participant
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
closes #11597
closes #11618
Since #11537, you can no longer introspect tokens created by another provider. This creates problems when using one OAuth2 provider to authenticate to an API protected by another provider.
My example is Stalwart mail server (which supports OAuth2 authentication), with Roundcube mail server. Currently, I have to use the userinfo endpoint, which is no longer recommended because Stalwart cannot check the audience of the token (see https://www.reddit.com/r/stalwartlabs/comments/1q8otw8/comment/nzfigmr/).
With this patch, you can now allow other providers tokens to be used at the introspection endpoint on a whitelist basis. This is in keeping with the security patch for #11537, but allows the flexibility of cross-provider token introspection.
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)