-
Notifications
You must be signed in to change notification settings - Fork 448
Fix AttributeError and signature mangling during construction of SOAP request #834
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
640fad3
to
c95093d
Compare
c95093d
to
44d967d
Compare
4 tasks
jonathanperret
added a commit
to proconnect-gouv/oidc2fer
that referenced
this pull request
Sep 18, 2025
The current version of pysaml2 (7.5.2) has an issue where AuthNRequests are both signed in the XML and with an extra `Signature` queryparam. This was reported initially in 2021: IdentityPython/pysaml2#819 And it was fixed by a changed in SATOSA: IdentityPython/SATOSA#380 But it reappeared apparently and the original reporter has a PR open against pysaml2 that is supposed to fix it: IdentityPython/pysaml2#973 They report that the regression was introduced in pysaml2 by IdentityPython/pysaml2#834 We try here to pin pysaml2 to the last version before this PR was merged. Unfortunately this is quite an old version, but from basic testing it seems to still be compatible with the current SATOSA version. Hopefully this can be temporary.
jonathanperret
added a commit
to proconnect-gouv/oidc2fer
that referenced
this pull request
Sep 25, 2025
The current version of pysaml2 (7.5.2) has an issue where AuthNRequests are both signed in the XML and with an extra `Signature` queryparam. This was reported initially in 2021: IdentityPython/pysaml2#819 And it was fixed by a changed in SATOSA: IdentityPython/SATOSA#380 But it reappeared apparently and the original reporter has a PR open against pysaml2 that is supposed to fix it: IdentityPython/pysaml2#973 They report that the regression was introduced in pysaml2 by IdentityPython/pysaml2#834 We try here to pin pysaml2 to the last version before this PR was merged. Unfortunately this is quite an old version, but from basic testing it seems to still be compatible with the current SATOSA version. Hopefully this can be temporary.
jonathanperret
added a commit
to proconnect-gouv/oidc2fer
that referenced
this pull request
Sep 25, 2025
The current version of pysaml2 (7.5.2) has an issue where AuthNRequests are both signed in the XML and with an extra `Signature` queryparam. This was reported initially in 2021: IdentityPython/pysaml2#819 And it was fixed by a changed in SATOSA: IdentityPython/SATOSA#380 But it reappeared apparently and the original reporter has a PR open against pysaml2 that is supposed to fix it: IdentityPython/pysaml2#973 They report that the regression was introduced in pysaml2 by IdentityPython/pysaml2#834 We try here to pin pysaml2 to the last version before this PR was merged. Unfortunately this is quite an old version, but from basic testing it seems to still be compatible with the current SATOSA version. This in turn forces us to also pin xmlschema to avoid IdentityPython/pysaml2#947 Hopefully this can be temporary.
jonathanperret
added a commit
to proconnect-gouv/oidc2fer
that referenced
this pull request
Sep 25, 2025
The current version of pysaml2 (7.5.2) has an issue where AuthNRequests are both signed in the XML and with an extra `Signature` queryparam. This was reported initially in 2021: IdentityPython/pysaml2#819 And it was fixed by a changed in SATOSA: IdentityPython/SATOSA#380 But it reappeared apparently and the original reporter has a PR open against pysaml2 that is supposed to fix it: IdentityPython/pysaml2#973 They report that the regression was introduced in pysaml2 by IdentityPython/pysaml2#834 We try here to pin pysaml2 to the last version before this PR was merged. Unfortunately this is quite an old version, but from basic testing it seems to still be compatible with the current SATOSA version. This in turn forces us to also pin xmlschema to avoid IdentityPython/pysaml2#947 Hopefully this can be temporary.
jonathanperret
added a commit
to proconnect-gouv/oidc2fer
that referenced
this pull request
Sep 25, 2025
The current version of pysaml2 (7.5.2) has an issue where AuthNRequests are both signed in the XML and with an extra `Signature` queryparam. This was reported initially in 2021: IdentityPython/pysaml2#819 And it was fixed by a changed in SATOSA: IdentityPython/SATOSA#380 But it reappeared apparently and the original reporter has a PR open against pysaml2 that is supposed to fix it: IdentityPython/pysaml2#973 They report that the regression was introduced in pysaml2 by IdentityPython/pysaml2#834 We try here to pin pysaml2 to the last version before this PR was merged. Unfortunately this is quite an old version, but from basic testing it seems to still be compatible with the current SATOSA version. This in turn forces us to also pin xmlschema to avoid IdentityPython/pysaml2#947 Hopefully this can be temporary.
jonathanperret
added a commit
to proconnect-gouv/oidc2fer
that referenced
this pull request
Sep 25, 2025
The current version of pysaml2 (7.5.2) has an issue where AuthNRequests are both signed in the XML and with an extra `Signature` queryparam. This was reported initially in 2021: IdentityPython/pysaml2#819 And it was fixed by a changed in SATOSA: IdentityPython/SATOSA#380 But it reappeared apparently and the original reporter has a PR open against pysaml2 that is supposed to fix it: IdentityPython/pysaml2#973 They report that the regression was introduced in pysaml2 by IdentityPython/pysaml2#834 We try here to pin pysaml2 to the last version before this PR was merged. Unfortunately this is quite an old version, but from basic testing it seems to still be compatible with the current SATOSA version. This in turn forces us to also pin xmlschema to avoid IdentityPython/pysaml2#947 Hopefully this can be temporary.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, sending SOAP requests using pysaml2 is near-impossible, because two bugs exist:
IDP.apply_binding
for soap withoutsign=True
and a pre-signed Message mangles/destroys the signature by removing the line-ends within the signature.IDP.apply_binding
's implementation of signing usinguse_soap
does not work currently, because instead ofnode_name
,class_name
is passed as a parameter tosecuritycontext.sign_statement
, and is raising anAttributeError
These two bugs are fixed with this PR
All Submissions: