Forums, Documentation & Knowledge Base - ComponentSpace

Exception: ComponentSpace.SAML2.Exceptions.SAMLSignatureException: Failed to verify the XML signature


https://componentspace.com/forums/Topic10751.aspx

By endritp - 3/5/2020

Hello,
One of the partners is getting the error message below. The cert is embedded in the body.

Can you explain if its related to the partner's cert being expired or something? 

ComponentSpace.SAML2 Verbose: 0 : 6760/49: 3/5/2020 11:03:25 AM: The X.509 certificate with subject name CN=*** and serial number 065B485D29F4EDE9737ED855FE0DB73C is embedded in the XML signature.
ComponentSpace.SAML2 Verbose: 0 : 6760/49: 3/5/2020 11:03:25 AM: Exception: ComponentSpace.SAML2.Exceptions.SAMLSignatureException: Failed to verify the XML signature. ---> System.Security.Cryptography.CryptographicException: An internal error occurred.

at System.Security.Cryptography.NCryptNative.OpenStorageProvider(String providerName)
at System.Security.Cryptography.CngKey.Import(Byte[] keyBlob, String curveName, CngKeyBlobFormat format, CngProvider provider)
at System.Security.Cryptography.X509Certificates.RSACertificateExtensions.GetRSAPublicKey(X509Certificate2 certificate)
at System.Security.Cryptography.X509Certificates.X509CertificateExtensions.GetAnyPublicKey(X509Certificate2 c)
at System.Security.Cryptography.Xml.SignedXml.GetPublicKey()
at System.Security.Cryptography.Xml.SignedXml.CheckSignatureReturningKey(AsymmetricAlgorithm& signingKey)
at ComponentSpace.SAML2.Utility.XmlSignature.Verify(XmlElement xmlElement, AsymmetricAlgorithm signingKey, ISignedXmlFactory signedXmlFactory, Boolean clone, Boolean declareAllNamespaces) in C:\Sandboxes\ComponentSpace\SAMLv20\Library\Utility\XmlSignature.cs:line 364
at ComponentSpace.SAML2.Utility.XmlSignature.Verify(XmlElement xmlElement, AsymmetricAlgorithm signingKey, ISignedXmlFactory signedXmlFactory) in C:\Sandboxes\ComponentSpace\SAMLv20\Library\Utility\XmlSignature.cs:line 860
--- End of inner exception stack trace ---
By ComponentSpace - 3/6/2020

Thanks for the update. I'm not sure what the issue was either but I'm glad the IIS restart resolved it.