doc update for dpop and token exchange#51043
Merged
Merged
Conversation
| s|Consents | Allowed for clients with `Consent required` as long as the user is already granted consent | Not allowed for clients with *Consent required* | ||
| s|Authorization | Verification that the requester client must be in the audience of the `subject_token`. Integration with client policies. No Fine-grained admin permissions | Based on fine-grained admin permissions version 1 | ||
| s|Revocation chain | Not available for access tokens. Available for refresh tokens | Not available for access nor refresh tokens | ||
| s|Sender-constrained tokens (DPoP, mTLS) | Supported. See <@links.securingapps id="dpop" />. | Not supported. The exchanged token is issued without any binding. |
Closes keycloak#50963 Closes keycloak#51004 Signed-off-by: Giuseppe Graziano <g.graziano94@gmail.com>
| will mean that the access token is valid. If the subject token is a JWT and if the provider has signature validation enabled, that will be attempted, | ||
| otherwise, it will default to also invoking on the user info service to validate the token. | ||
|
|
||
| WARNING: The legacy external-to-internal token exchange does *not* validate the `aud` (audience) claim of the `subject_token`, so an ID token issued by the external identity provider to a different client will be accepted as long as signature and expiry checks pass; restrict `token-exchange` permissions to only the clients that genuinely require them. |
| s|Consents | Allowed for clients with `Consent required` as long as the user is already granted consent | Not allowed for clients with *Consent required* | ||
| s|Authorization | Verification that the requester client must be in the audience of the `subject_token`. Integration with client policies. No Fine-grained admin permissions | Based on fine-grained admin permissions version 1 | ||
| s|Revocation chain | Not available for access tokens. Available for refresh tokens | Not available for access nor refresh tokens | ||
| s|Sender-constrained tokens (DPoP, mTLS) | Supported. See <@links.securingapps id="dpop" />. | Not supported. The exchanged token is issued without any binding. |
mposolda
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 #51004
Closes #50963