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.
JwtSecurityTokenHandler.CreateJwt no longer sets JwtSecurityToken.SigningCredentials
See original GitHub issue_Moved from https://github.com/aspnet-contrib/AspNet.Security.OpenIdConnect.Server/issues/232._
The recent changes introduced by @brentschmaltz in this commit broke CreateJwt, which is no longer able to flow the SigningCredentials taken as a parameter to the JwtSecurityToken it returns due to the (weird) lossy serialization + deserialization process it’s now using:
This is obviously a serious regression since calling WriteToken to serialize the JWT now results in a compact JWT that lacks the signature.
Issue Analytics
- State:
- Created 7 years ago
- 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
@PinpointTownes It was committed today. Should be in tonight’s myget.release.
Unfortunately, trying to use the azureadwebstacknightly feed - as I had initially suggested - will cause more pain because ASOS needs to be fixed to react to a breaking change in
IdentityModel: https://github.com/aspnet-contrib/AspNet.Security.OpenIdConnect.Server/issues/232#issuecomment-207046066Sadly, since the updated package is not on the aspnetcidev feed we use, I can’t push the fix ATM.