Introduce a new DisableUserinfo option in RefreshTokenAuthenticationRequest to allow refreshing tokens acquired during a client credentials flow #1955
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.
Using refresh tokens with the client credentials grant is discouraged by the OAuth 2.0 specification but some providers are known to use them. So far, using the
AuthenticateWithRefreshTokenAsync()
API with a refresh token acquired during a client credentials flow wasn't possible without writing an event handler to disable userinfo retrieval as OpenIddict automatically performs a userinfo request.This PR introduces a new
DisableUserinfo
option inRefreshTokenAuthenticationRequest
that allows skipping the userinfo request.