Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a new DisableUserinfo option in RefreshTokenAuthenticationRequest to allow refreshing tokens acquired during a client credentials flow #1955

Merged
merged 1 commit into from
Jan 15, 2024

Conversation

kevinchalet
Copy link
Member

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 in RefreshTokenAuthenticationRequest that allows skipping the userinfo request.

@kevinchalet kevinchalet added this to the 5.1.0 milestone Jan 15, 2024
@kevinchalet kevinchalet self-assigned this Jan 15, 2024
@kevinchalet kevinchalet force-pushed the refresh_token_userinfo branch 2 times, most recently from 6ea34d7 to 159b402 Compare January 15, 2024 08:29
…equest to allow refreshing tokens acquired during a client credentials flow
@kevinchalet kevinchalet merged commit 7af133f into openiddict:dev Jan 15, 2024
6 checks passed
@kevinchalet kevinchalet deleted the refresh_token_userinfo branch January 15, 2024 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant