-
Notifications
You must be signed in to change notification settings - Fork 14
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
switch from xmldom to @xmldom/xmldom #12
Comments
Thank you for the heads up. I would absolutely merge a change if someone made a pull request. At this point in time I don't maintain any projects that use SAML in a JS environment and I've also archived all of those projects from my dev machine after buying a new one so just the setup alone would be tons of work for me. I keep this project up because I know there aren't any easy to use SAML libraries for Node around. If you or others think it's better I take this code down rather than let it hang out on the web with a vulnerability I'm open to that as well. |
Thank you for the heads up. In my case, when I use the new version of @xmldom/xmldom, it doesn't work for some users, while it works in other cases. When I use the old version of xmldom, it works for all users. |
Hi got the solution old changes // Saml2js.parse var attributes = xpath.select('//[local-name() = "AttributeStatement"]/', doc); latest changes in code // Saml2js.parse var attributes = xpath.select('//[local-name() = "AttributeStatement"]/', doc); return profile; only this line will change and now code will work both samle |
xmldom is no longer maintained and is affected by https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39353
Please switch to https://www.npmjs.com/package/@xmldom/xmldom - the upgrade should be trivial as @xmldom/xmldom
is developed by the same team and is fully backwards compatible.
The text was updated successfully, but these errors were encountered: