spring-projects / spring-projects/spring-security
OIDC token-request client-secret %3D instead of = for padding
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
When sending an OIDC token-request including client-secret (and client-id), the configured client-secret is changed: Any ending = is converted to %3D
To Reproduce
authenticate against an OIDC provider that requires
spring.security.oauth2.client.registration.<provider>.client-authentication-method=client_secret_post
with a client-secret that ends with padding character =
That will result in a token-request where the padding character is replaced by unicode %3D
Expected behavior
padding character for client-id should not be converted to unicode
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing an OIDC token request using client_secret_post and a client-secret ending in =; done means the request preserves the padding character as = rather than encoding it as %3D.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100