Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
X509SecurityKey.KeyId update breaks IdentityServer4 clients
See original GitHub issueI’ve updated Microsoft.IdentityModel.Tokens from version 5.3.0 to 5.4.0 and the KeyId has been changed from thumbprint to base64 encoded hash of the certificate. See: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/commit/760fa3046cc36591c9f7835031745fcd625cf6ec#diff-ad9f507af4d8334a3a5dbcafbb0ded30
I’ve got IdentityServer4 running and this changes the kid (KeyId) in the openid connect endpoint .well-known/openid-configuration/jwks which breaks JWT validation on my clients. The currently logged in users have a token from a different (now non-existing) keyid when I deploy this update.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yea, this is a breaking change in a patch. Why was this change needed?
This change will brake any existing application which uses X509SecurityKey and expects to validate certificate Thumbprints through the originally offered KeyId.
E.g. this change could likely also break Identity Server 4’s commercial SSO plugin if the receiving party validates for thumbprints.