Skip to content
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

Setting requestedAuthnContext #427

Closed
tibra opened this issue Dec 12, 2017 · 2 comments
Closed

Setting requestedAuthnContext #427

tibra opened this issue Dec 12, 2017 · 2 comments

Comments

@tibra
Copy link

tibra commented Dec 12, 2017

On an authentication request from our ruby-saml SP, the IdP (a NetIQ instance) instantly redirects back to the SP without offering a login form. When inspecting the params, I'm seeing a SAMLResponse with a payload error:
The status code of the Response was not Success, was Responder.

The IdP logs are indicating
urn:oasis:names:tc:SAML:2.0:status:NoAuthnContext.

On other SPs where login forms are successfully presented, the IdP is reporting:
urn:oasis:names:tc:SAML:2.0:status:Success

Answers to similar problems in php-saml and passport-saml suggest to set requestedAuthnContext to false. Is there any way of setting the requested authn context to a similar setting in ruby-saml?

What we've tried so far:

  • setting authn_context to false
  • setting authn_context to "urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport"
  • setting authn_context_comparison to minimum
  • double checking the signing and certificates

Thank you kindly!

@pitbulk
Copy link
Collaborator

pitbulk commented Dec 15, 2017

By default ruby-saml does not assign any value to the authn_context and authn_context_decl_ref.

That are reviewed on the create_xml_document method of authrequest.rb to create the AuthNRequest with RequestedAuthnContext or not.

So if those values are false or null, the generated AuthNRequest shouldn't contains an RequestedAuthnContext element. If it does, review if you are using not directly ruby-saml but a framework, if it set values to those setting parameters.

@tibra
Copy link
Author

tibra commented Dec 19, 2017

Thank you for pointing to the defaults and clearing things up, @pitbulk . After re-importing our metadata, this issue has been resolved :-)

@tibra tibra closed this as completed Dec 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants