fix: respect token_endpoint_auth_method=none when client_secret exists #1846
+72
−3
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.
Summary
Fix
ClientAuthenticatorto properly honortoken_endpoint_auth_method="none"even when aclient_secretis stored for the client.Problem
When a client has
token_endpoint_auth_method="none"but also has aclient_secretstored (e.g., from a previous configuration or edge case), the authenticator incorrectly raises "Client secret is required" error.The logic was:
token_endpoint_auth_method="none"→ skip extracting credentials from request ✓client.client_secretexists → raise error if no credentials provided ✗If
token_endpoint_auth_method="none"is set, it should never check for aclient_secreton the request.Solution
Add a check for
token_endpoint_auth_method != "none"before validating the client_secret requirement: