Deprecate introspection endpoint 'jwt' extension#51027
Merged
Merged
Conversation
closes keycloak#51026 Signed-off-by: mposolda <mposolda@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Documents the deprecation of the non-standard JWT introspection extension and recommends token exchange as its replacement.
Changes:
- Adds deprecation guidance to Admin UI help text.
- Updates securing-apps and upgrade documentation.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
messages_en.properties |
Adds deprecation guidance to the client setting. |
available-endpoints.adoc |
Warns endpoint users about deprecation. |
changes-26_8_0.adoc |
Adds an upgrade-guide deprecation notice. |
Comment on lines
+95
to
+96
| WARNING: The functionality of invoking introspection endpoint with `Accept: application/jwt` header is deprecated now and will be removed in the future. Please | ||
| use <@links.securingapps id="token-exchange" /> {section}. |
Contributor
Author
There was a problem hiding this comment.
IMO will be better to not specify concrete version for removal in the documentation, release notes and tooltip. As specifying concrete version in all those places means less flexibility (EG. if we want to remove this later for some reason...)
Comment on lines
+32
to
+34
| Proprietary {project_name} extension to invoke introspection endpoint with the HTTP header `Accept: application/jwt` instead of `Accept: application/json` is | ||
| deprecated now. In case you have lightweight access token, which you want to exchange for the proper access token, it is instead recommended to use the | ||
| link:{securing_apps_token_exchange_link}[Token Exchange]. |
| lightweightAccessTokenHelp=If it is On, lightweight access tokens are always used. If it is Off, they are not used by default, but it is still possible to enable them with client policy executor. | ||
| supportJwtClaimInIntrospectionResponse=Support JWT claim in Introspection Response | ||
| supportJwtClaimInIntrospectionResponseHelp=If it is On, introspection requests which use the header 'Accept: application/jwt' will also contain a claim named "jwt" with the claims of the introspection result encoded as JWT access token. | ||
| supportJwtClaimInIntrospectionResponseHelp=If it is On, introspection requests which use the header 'Accept: application/jwt' will also contain a claim named "jwt" with the claims of the introspection result encoded as JWT access token. This switch is deprecated. Please use token exchange instead of this functionality. |
lhanusov
approved these changes
Jul 21, 2026
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
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.
closes #51026