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

Client request to token endpoint does not encode clientKey and secret properly #1532

Open
hjalet opened this issue Mar 16, 2020 · 0 comments

Comments

@hjalet
Copy link

hjalet commented Mar 16, 2020

In the OpenID Connect Client:
When using a shared secret to request tokens at the token endpoint after a successful login,
The clientKey and Secret does not seem to be encoded correctly.
So a '/' in the secret is correctly encoded to %2F
While '+' and '=' signs in the client secret is not encoded at all.

The encoding takes place in line 248 in OIDCAuthenticationFilter class

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant