-
Notifications
You must be signed in to change notification settings - Fork 421
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
Signing in XMLSecurity based saml2 #901
Comments
Also, to be able to check signed assertions, I had to:
in the validate_signature method of the CryptoBackendXMLSecurity object. Those lines are already there in the equivalent method of the CryptoBackendXmlSec1 object
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code Version
Version 7.4.1
Expected Behavior
We're implementing a SP under Windows. Since using xmlsec1 version under Windows gives us a lot of troubles, we were trying to use, as a crypto backend, "XMLSecurity".
At least for signing an AuthnRequest, it should work.
Current Behavior
We're getting
Possible Solution
It seems that the sec_backend of the sec object is not initialized in case of "XMLSecurity"
In sigver.py, in function security_context (line 927 in my version), if we move the block of code:
(at lines 962-970 in my version), outside the if-elif-else, the signing works fine.
As a recap, if we change from
to
we are able to have XMLSecurity to wotk correctly (for signing, at least)
The text was updated successfully, but these errors were encountered: