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

UTF-8 encoding introduces incompatible Authorization header #12566

Closed
jochan-clgx opened this issue Jan 19, 2023 · 1 comment
Closed

UTF-8 encoding introduces incompatible Authorization header #12566

jochan-clgx opened this issue Jan 19, 2023 · 1 comment
Labels
for: stackoverflow A question that's better suited to stackoverflow.com

Comments

@jochan-clgx
Copy link

I am migrating an application from Spring Boot 2.5.14 to 3.0.1 which brings in Spring Security 6.0.1. I experienced that our test cases no longer getting authenticated with our existing client-id and client-secret. After a debugging session, I realized that there are new changes with spring-security-oauth2-client

It introduces the UTF-8 encoding for authorization header which encodes most of our existing client-secret differently compare to Spring Security 5.5.x. My apology if I missed anything but if it is an issue, may I ask if there is any temporary workaround at the moment?

Thank you,

@jochan-clgx jochan-clgx added status: waiting-for-triage An issue we've not yet triaged type: bug A general bug labels Jan 19, 2023
@sjohnr
Copy link
Member

sjohnr commented Jan 20, 2023

@jochan-clgx, thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add a minimal sample that reproduces this issue if you feel this is a genuine bug.

Also, please see this comment and #11440 generally for a possible answer to your question. Also see this comment for additional details on the workaround.

@sjohnr sjohnr closed this as completed Jan 20, 2023
@sjohnr sjohnr added for: stackoverflow A question that's better suited to stackoverflow.com and removed status: waiting-for-triage An issue we've not yet triaged type: bug A general bug labels Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: stackoverflow A question that's better suited to stackoverflow.com
Projects
None yet
Development

No branches or pull requests

2 participants