Hi all,
I know that this message usually comes up when the SHA-256 is not enabled, but it should be. I went through the guide:
http://www.componentspace.com/Forums/30/SHA256-XML-Signature-Support
I am running .NET 4.0 versions of the ComponentSpace.SAML2.dll
The .net framework being used to run the web app is .Net 4.0.
SHA-1 version of a response works perfectly fine.
Is there something else I have to enable to get SHA-256 response to work?
Thanks!
[quote][/quote]
Hi all,
I know that this message usually comes up when the SHA-256 is not enabled, but it should be. I went through the guide:
http://www.componentspace.com/Forums/30/SHA256-XML-Signature-Support
I am running .NET 4.0 versions of the ComponentSpace.SAML2.dll
The .net framework being used to run the web app is .Net 4.0.
SHA-1 version of a response works perfectly fine.
Is there something else I have to enable to get SHA-256 response to work?
Thanks!
I know that this message usually comes up when the SHA-256 is not enabled, but it should be. I went through the guide:
http://www.componentspace.com/Forums/30/SHA256-XML-Signature-Support
I am running .NET 4.0 versions of the ComponentSpace.SAML2.dll
The .net framework being used to run the web app is .Net 4.0.
SHA-1 version of a response works perfectly fine.
Is there something else I have to enable to get SHA-256 response to work?
Thanks!
So I looked in the web.config file and the machineKey element does have the validation="SHA1". Would that effect the verify? I thought the privateKey from the certificate file would determine how to verify the signature? If this is the problem is there a utility within ComponentSpace that will determine the algorithm and use it accordingly or at least a method I can pass the algorithm to use at run time?
THanks!
Are you attempting to generate or verify a SHA-256 XML signature?
If generating a signature, there may be an issue with the wrong cryptographic service provider (CSP) being associated with the private key.
This can be resolved using openssl.
http://www.componentspace.com/Forums/1578/SHA256-and-Converting-the-Cryptographic-Service-Provider-Type
If verifying a signature, it’s possible you’re using an earlier version of the SAML2 DLL which doesn’t include automatic support for SHA-256.
To help resolve the issue, please enable SAML trace and send the generated log file as an email attachment to our support email address.
http://www.componentspace.com/Forums/17/Enabing-SAML-Trace
The machine key isn’t relevant.