-
-
Notifications
You must be signed in to change notification settings - Fork 569
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
uninitialized constant XMLSecurity::SignedDocument::XPath #1
Comments
ekolve, I just added a test case to try and reproduce your observation but could not. could you try forking the project and run the tests? what kind of environment are you deploying the gem in? |
I could reproduce under 1.9.2, not sure why it works under REE but that's a different story. Pushed the fix and will ask gem maintainer to release 0.2.2. Thanks for the heads up. |
thanks for taking care of it. |
bracken
referenced
this issue
in instructure/ruby-saml
Jun 15, 2011
phinze
pushed a commit
to phinze/ruby-saml
that referenced
this issue
Feb 15, 2013
Accept SAML assertions from Shibboleth IdPs.
echorink
referenced
this issue
in echorink/ruby-saml
Jun 5, 2013
permit NoPassive status codes in response
ghost
mentioned this issue
May 2, 2015
pitbulk
pushed a commit
that referenced
this issue
Jun 30, 2015
According to the xsd, the issuer has to be before the status
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While trying to validate a SAML Response I received the following error:
/usr/lib/ruby/gems/1.8/gems/ruby-saml-0.2.1/lib/xml_sec.rb:55:in
validate_doc': uninitialized constant XMLSecurity::SignedDocument::XPath (NameError) from /usr/lib/ruby/gems/1.8/gems/ruby-saml-0.2.1/lib/xml_sec.rb:48:in
validate'from /usr/lib/ruby/gems/1.8/gems/ruby-saml-0.2.1/lib/onelogin/saml/response.rb:21:in `is_valid?'
I'm running Ruby 1.8.7 p302 with ruby-saml 0.2.1. What seemed to fix this was when I prepended all instances of 'XPath' with 'REXML::'.
The text was updated successfully, but these errors were encountered: