We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi there, Given an invalid SAMLResponse, the Response object now raises REXML::ParseException on rexml 3.3.9.
REXML::ParseException
1) SamlController POST #consume without an original page when invalid response Failure/Error: @sso_response ||= OneLogin::RubySaml::Response.new( params[:SAMLResponse], settings: sso_config.saml_settings, allowed_clock_drift: 60, skip_subject_confirmation: true ) REXML::ParseException: Malformed XML: Content at the start of the document (got 'invalid') Line: 1 Position: 7 Last 80 unconsumed characters: # /usr/local/bundle/gems/rexml-3.3.9/lib/rexml/parsers/baseparser.rb:517:in `pull_event'
Which means the response interface is now broken on 1.17.0
1.17.0
response.is_valid?
Related to ruby/rexml#211
TIA
The text was updated successfully, but these errors were encountered:
Hi @msxavi
We could catch the REXML::ParseException when building the Response (and others), and raise an ArgumentError similar than
raise ArgumentError.new("Response XML is invalid")
as we do here
Sorry, something went wrong.
No branches or pull requests
Hi there,
Given an invalid SAMLResponse, the Response object now raises
REXML::ParseException
on rexml 3.3.9.Which means the response interface is now broken on
1.17.0
Related to ruby/rexml#211
TIA
The text was updated successfully, but these errors were encountered: