-
-
Notifications
You must be signed in to change notification settings - Fork 465
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
NoAuthnContext #62
Comments
Based on the error that you posted
I can say that ADFS received an AuthNRequest with an AuthnContext that is not supported (maybe due a configuration problem). The Status is the way how an IdP can provide to the SP that something went wrong, in this case By default, OneLogin's SP is configured to send an AuthNRequest with In order to fix it you have 2 choices:
|
After setting Thanks. |
We too notice this problem with many customers, especially the ones with kerberos, cert and other forms of authentication. This fails even if the PasswordProtectedTransport is enabled on IDP as we are using exact. The default set by onelogin libary should be requestedAuthnContext to false by default or all the contexts should be sent for selecting any. The default's should not be very restrictive. Can we have this changed in the next version, please? |
I agree that set "exact PasswordProtectedTransport" as default requestedAuthnContext was not the right decision. |
I am not all that familiar with SAML so bare with me.
I just installed the https://github.com/aacotroneo/laravel-saml2 package with a new instance of Laravel 5. Unfortunately I am getting this error.
The status code of the Response was not Success, was Responder -> urn:oasis:names:tc:SAML:2.0:status:NoAuthnContext
Any thoughts on how what this error means? I am sure it is some type of configuration issue. I am just not familiar enough with SAML to know which side the error is coming from ADFS IDP or my OneLogin configuration.
I was able to connect and login successfully with a PHPSimpleSaml implementation. However, OneLogin gives me more flexibility. This is why I wanted to use this package.
I would appreciate any suggestions. Thanks.
The text was updated successfully, but these errors were encountered: