-
Notifications
You must be signed in to change notification settings - Fork 173
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
Accept existing xml prefixes to avoid adding to signature #171
Conversation
Shouldn't Travis use a more recent node version? 0.10 and 0.12 are really old and not supported anymore. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm - I would strongly prefer that you keep the old node versions just because this library is used mostly in enterprise environments, which tend to be very slow in taking up new releases.
If I make this work on the old node version, would you accept it? I'm happy to change it then. |
I would - and I was planning to make the changes in your branch if not for life getting in the way. Feel free to go ahead of me. |
It should be solved now. Thanks for maintaining this library! |
This update will pick up the following changes: node-saml/xml-crypto#171 node-saml/xml-crypto#179 node-saml/xml-crypto#183
Not sure if this is the best way, but it does work.
This adds an extra option
existingPrefixes
.I also added this to the README and there is a test.
Fixes #170