OAuth2Client: use correct auth method for token introspection #662
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.
When token introspection was introduced in 6f5d19a, using the code that previously only handled token revocation, the new
_handle_token_hint
method that does the work for bothintrospect_token
andrevoke_token
kept usingself.revocation_endpoint_auth_method
unconditionally if noauth
was passed in with the introspect or revoke request. This seems to be wrong, introspecting a token should use thetoken_endpoint_auth_method
.This leaves the fallback to
revocation_endpoint_auth_method
in_handle_token_hint
because adjusting its signature to makeauth
compulsory would be awkward, but it's not expected ever to be used.What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)