-
-
Notifications
You must be signed in to change notification settings - Fork 164
Signature is invalid #10
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
Comments
var assertionValidationResult = ValidateXmlSignature(assertionElement); |
Ran into this problem with a response from OpenAM. ADFS worked fine, but all OpenAM responses failed signature validation for the assertion. From what I can tell, the issue is with canonicalization and the way SignedXml handles namespace prefixes in XmlElements when the context is the assertion element and not the full document. e.g. OpenAM responds with a Workaround is to throw the OpenAM assertion into its own document, and then validate the signature. You can do that by overloading
And then use the class in place of the base Saml2AuthnResponse:
|
Fix added to 69810b0 by loading Assertion in new XmlDocument before signature validation. |
Little confused, why is this fix only implemented for .NET Framework? Have hit this problem with ASP.NET Core 3.1 and found that @Spksh's suggested fix above was the answer. After digging a bit deeper realised the fix is in the codebase in the |
Hi!
I tried to validate the SAML Response and exception thrown:
Code:
SAMLResponse:
IdP EntityId: https://lastpass.com/saml/idp
SP EntityId: https://dev.findo.io
SP Consume Service Endpoint: https://e2757cbf.ngrok.io/Saml2/Consume
IdP X.509 certificate:
Thanks in advance!
The text was updated successfully, but these errors were encountered: