-
-
Notifications
You must be signed in to change notification settings - Fork 561
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
response.validate! call fails #70
Comments
I should add I am getting <UNDEFINED> ... </>
from
response.document.inspect |
Yeah I'm getting the same thing too...
from response.rb:
The above line is returning nothing... I get this hex data for @response:
Unsure exactly what to do with this. If it matters, it's ADFS on windows 2012 R2 Anyone have any clues about this? |
@naemono Can you install the SAML Tracer Firefox Plugin (https://addons.mozilla.org/es/firefox/addon/saml-tracer/) and send as the base64 encoded SAML Response? |
Thanks for looking into this. I assume you're wanting this:
This is from the 302 back to my application: |
I finally figured out what was going on. I was not hitting https://myapp/auth/saml to generate the saml2 request (302 to adfs), but hitting https://myadfs/adfs/ls/idpinitiatedsignon to generate the saml callback, which turned out to be generating saml1 responses, which was causing this error. The documentation is seriously lacking here for ADFS (I'll generate a pull request for omniauth-saml readme) There doesn't seem to be way to force adfs to use saml2 when hitting the idpinitiatedsignon page without this gem creating the proper parameters sent to adfs:
Anyways, thanks for the work on this gem... |
thanks for the followup @naemono! going to close this for now. |
We were running into this issue as well when validating documents without a signature ( #66 fixes this. Try upgrading to |
@alperkokmen Typo? |
@tboyko nope, |
Hi,
I am trying to use ruby-saml with a custom OmniAuth Strategy. I am using version 0.7.2
In my heroku logs I see
Below is what my OmniAuth callback phase looks like. The failure seems to be around the response.validate! call. Any thoughts on why this is happening? Problem in my code or in ruby-saml? I know I can receive the SAML response if I comment out that
call. But I am trying to understand the validate method. And specifically what steps I need to take to ensure the SAML assertion my application is receiving is properly signed and trustworthy.
The text was updated successfully, but these errors were encountered: