Replies: 2 comments
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Because I need it for another authentication. We have 2 ways of authentication
Keep in mind, one is wih Bearer and the other is with AzureAd registered To answer your second question, Why do you provide the StS signing keys? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi I am struggling with a log problem and I hope you guys can help me.
I've updated from version 1.24.1 to 1.25.1
Everything works but I get the errors below. Is this some sort of false positive? What is happening here?
My steps:
The 3 steps work. They just work. If I use a invalid token it does not work. This is also perfect. Has someone an Idea to why these errors trigger from 1.25.1?
Errors:
IDX10503: Signature validation failed. Token does not have a kid. Keys tried........
IDX10634: Unable to create the SignatureProvider.
Algorithm: 'HS512', SecurityKey: 'Microsoft.IdentityModel.Tokens.X509SecurityKey, KeyId: 'OzZ5Dbmcso9Qzt2ModGmihg30Bo', InternalId: 'OzZ5Dbmcso9Qzt2ModGmihg30Bo'.'
is not supported. The list of supported algorithms is available here: https://aka.ms/IdentityModel/supported-algorithms
IDX10634: Unable to create the SignatureProvider.
Algorithm: 'HS512', SecurityKey: 'Microsoft.IdentityModel.Tokens.RsaSecurityKey, KeyId: 'DqUu8gf-nAgcyjP3-SuplNAXAnc', InternalId: '8cTdfkGpvGb-S7Jm4j2Qx_vFGaTWhyHvzyUNxDldt00'.'
is not supported. The list of supported algorithms is available here: https://aka.ms/IdentityModel/supported-algorithms
my configuration:
Beta Was this translation helpful? Give feedback.
All reactions