We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When you use a question mark in the client_secret with OAuth2, the question mark doesn't get encoded properly.
% echo -n '?:?' | base64 Pzo/
When retrieving the base64 encoded string from Infinity: authorization: "Basic JTNGOiUzRg=="
authorization: "Basic JTNGOiUzRg=="
Decoding this string results in:
% echo -n 'JTNGOiUzRg==' | base64 --decode %3F:%3F%
The text was updated successfully, but these errors were encountered:
After some more testing it seems to happen with other special characters as well, exclamation mark (!) doesn't work either
Sorry, something went wrong.
No branches or pull requests
Describe the bug
When you use a question mark in the client_secret with OAuth2, the question mark doesn't get encoded properly.
Steps to reproduce
Sample Data
When retrieving the base64 encoded string from Infinity:
authorization: "Basic JTNGOiUzRg=="
Decoding this string results in:
Version Details:
The text was updated successfully, but these errors were encountered: