JWKS endpoint escapes '+' as '\u002B' in x5c field #470
Unanswered
asos-jasperdeluna
asked this question in
IdentityServer
Replies: 1 comment 2 replies
-
|
Thanks very much for this detailed bug report! I agree with your reading of the standards. We should not be escaping the plus character in this way, and it does indeed look like it is behavior that we are getting from System.Text.Json. My hypothesis is that this changed when the underlying System.IdentityModel.* libraries changed to use System.Text.Json. My advice for a short-term workaround is to go with middleware (your option 2). Meanwhile, the development team is working on a fix. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The JWKS endpoint returns \u002B instead of literal + in Base64-encoded x5c certificate values:
"x5c": ["MIIF...CNDO10w\u002BRnuMEzkifo..."]
I think the root cause was raised here: dotnet/runtime#50998
We've identified some potential workarounds. Could you advise which approach you'd recommend?
Environment
References
Beta Was this translation helpful? Give feedback.
All reactions