Skip to content
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

Fixes issue with SAMLSignature method not using default transformations #473

Merged
merged 1 commit into from
Apr 10, 2022

Conversation

stjeffrey
Copy link
Contributor

This seems to be a bug where the method sets up a default array of transformations when none is passed in the options but then this code ignores the defaults and uses the ones from the options passed which could be undefined. The addReference then possibly passes an undefined transformations which xml-crypto library only adds 'http://www.w3.org/2001/10/xml-exc-c14n#' instead of 'http://www.w3.org/2001/10/xml-exc-c14n#' and 'http://www.w3.org/2000/09/xmldsig#enveloped-signature' defined in this codebase's constructSAMLSignature.

…ansformations when none is passed in the options but then this code ignores the defaults and uses the ones from the options passed which could be undefined. The addReference then possibly passes an undefined transformations which xml-crypto library only adds 'http://www.w3.org/2001/10/xml-exc-c14n#' instead of 'http://www.w3.org/2001/10/xml-exc-c14n#' and 'http://www.w3.org/2000/09/xmldsig#enveloped-signature' defined in this codebase's constructSAMLSignature.
@tngan tngan self-requested a review February 18, 2022 20:25
@tngan tngan self-assigned this Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants