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.
Bring back SecurityKey.IsSupportedAlgorithm
See original GitHub issueWhen fixing ASOS to use the newest IM bits, I had to replace SecurityKey.IsSupportedAlgorithm by the new syntax.
key.IsSupportedAlgorithm(SecurityAlgorithms.RsaSha256Signature)
->
key.CryptoProviderFactory.IsSupportedAlgorithm(SecurityAlgorithms.RsaSha256Signature)
Unfortunately, it doesn’t work at all because the key itself is not flowed up to CryptoProviderFactory.IsSupportedAlgorithm so it always returns false even if the key is a RSA key.
You now have to use this extremely weird and error-prone syntax:
key.CryptoProviderFactory.IsSupportedAlgorithm(SecurityAlgorithms.RsaSha256Signature, key)
@brentschmaltz @tushargupta51 @polita any chance we can reintroduce SecurityKey.IsSupportedAlgorithm for RTM?
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (11 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
@kevinchalet I’ll get it in…
@brentschmaltz thanks! I can confirm the new API works like a charm 🎉