Add refreshTokenWithClientId option, to send client_id when using a refresh token #175
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.
Some OAuth providers (e.g. Keycloak) require that client_id is sent when using a refresh token.
This patch adds the
refreshTokenWithClientId
option that may be used similarly to therefreshTokenWithCredentials
.When
true
, the request body for the token refresh will also send aclient_id
parameter fetched from the state.I have locally tested this patch and it produces the desired behaviour, though I've not commit the packed dist bundle files yet.
The
refreshTokenWithCredentials
option wouldn't be suitable when using a public client as no credentials are known.Evidence of Keycloak's behaviour may be found on the discourse.