-
Notifications
You must be signed in to change notification settings - Fork 1.3k
client_secret like "Abc123++" get token failed #568
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
Comments
Hi @funs690. The converter is implemented to spec, per RFC 6749, Section 2.3.1. You can provide your own converter if you wish to deviate from the url encoding/decoding specified by the spec. For example: OAuth2AuthorizationServerConfigurer<HttpSecurity> authorizationServerConfigurer =
new OAuth2AuthorizationServerConfigurer<>();
authorizationServerConfigurer.clientAuthentication(clientAuthentication -> clientAuthentication
.authenticationConverter(new MyClientSecretBasicAuthenticationConverter())); If you are interested in learning more about customizing client authentication, please up-vote #540, as we are currently prioritizing what guides we work on for our reference documentation based on community feedback. I'm going to close this issue, as the implementation is working according to the specification. |
Hi @sjohnr, I am facing the same issue and I tried to implement my own
However, it always defaults to |
@shmonika, did you intend to put this code in the |
ClientSecretBasicAuthenticationConverter line 88-89
"Abc123++" after URLDecoder.decode change to "Abc123 "
###############
Basic Authentication set client_id and client_secret in the header. So no need to URLDecoder.decode again!
The text was updated successfully, but these errors were encountered: