-
Notifications
You must be signed in to change notification settings - Fork 101
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
Why is SSPI enabled per default? #132
Comments
I broke this - and I'm sort of stuck on how to best fix it. My thoughts here: I don't actually have an SSPI environment, so I can't say when the header is required. I know that in my case (and, according to the comments here, others) the header causes issues. I just trusted the comment & documentation which says that SSPI should be on by default and the header is required when using it. |
I am having a related issue when using AzureMFA Authentication.
I was getting this response.
I went and updated this file to print the response https://gist.github.com/lmayorga1980/ff6adfe00052a8b462b43723b836e77e Maybe there needs to be another property to be set? At this time, the best I can do is use an HTTP Packet Trace on my browser to see if it's sending some extra headers |
@lmayorga1980 Did you try with '--no-sspi' ? |
aws-adfs: 1.18.1 Maybe an older version?
I tried |
any 📰 @kfattig ?? |
The login flow in _azure_cloud_mfa_authenticator is broken unless the --no-sspi is given.
I'm not sure if this was the intended behaviour or not, but previously in html_roles_fetcher the User-Agent was not set since the import
from requets_negotiate_sspi import HttpNegotiateAuth
failed. The new behaviour now sets the header since sspi is set to True in thefetch_html_encoded_roles
which (by some reason unknown to me) breaks the login - after password is given, "This account does not have access to any roles" is received instead of having a prompt for MFA.Was the intention to have sspi enabled per default (it seems to be set in the
get_prepared_config
function in prepare.py)?The text was updated successfully, but these errors were encountered: