-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DigestAlgorithm cannot be determined for SigningAlgorithm PS256 #1367
Comments
After investigating a little further, it seems that the error message is a good indicator of what is going wrong. The Saml2/legacy/Sustainsys.Saml2.Metadata/Helpers/XmlHelpers.cs Lines 586 to 598 in 3bedefb
Is there a possibility to either (1) set the DigestAlgorithm in the config or (2) change the way the Digest-Algorithm is determined? The external Idp does not allow for any other Signing- or DigestAlgorithms. |
This is a scenario that is new to me. There is no way to handle this in the 1.x or 2.x versions. However, I would be happy to include it in 3.x. The code for XML signature handling is available in the |
Hello @ritocesura, I have the same problem. Do you have any solution? |
I think I have a similar problem. I need to use "http://www.w3.org/2007/05/xmldsig-more#sha256-rsa-MGF1" but I get the following errors using .NET 8.
Were you able to solve it in your scenario, @ritocesura? (@LeThai96) |
@zesaro as I know, the sha256-rsa-MGF1 algorithm is not supported by .NET. I have to switch to a different library. You can take a look at ComponentSpace, they support the algorithm which is implemented with BouncyCastle.NET |
Sustainsys.Saml2.AspNetCore2
Version 2.9.0
The SAML configuration of the service provider looks as follows:
I need the AuthnRequest to be signed with PS256 (sha256-rsa-MGF1). But when the application tries to sign, the following exception is thrown:
System.InvalidOperationException: Unable to find a digest algorithm for the signing algorithm http://www.w3.org/2007/05/xmldsig-more#sha256-rsa-MGF1
Can you kindly guide me on what else I need to configure to have my AuthnRequest signed with PS256 algorithm?
The text was updated successfully, but these errors were encountered: