-
Notifications
You must be signed in to change notification settings - Fork 140
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
o365 plugin does not work anymore #68
Comments
Interesting. I opened a similar issue: #67. Do you think what I am seeing is because of what actually Microsoft implemented? |
Confirming here that with valid creds Credmaster still says authentication failed using the o365 plugin. |
I think the best alternative is to use the MSOL plugin. |
The MSOL and AzureSSO plugins still work. However, both trigger Smart Lockout after about 10 failed logins, which the o365 plugin did not. It's a shame; it appears the era of easy Microsoft spraying are over (unless anyone else has found a way to bypass Smart Lockout that I've missed). |
Hey everyone, you're all correct, it does appear that the |
Tagging all those above: @TwistedSim @alecmoran1 @LukeLauterbach @kpomeroy1979 @TheToddLuci0 Would the community prefer this plugin be simply removed, have a big "WARNING" sign upon running (but still running as usual), or just run with an error message stating "this plugin is no longer supported, see MS docs: here" |
According to Microsoft, no one can enable the Basic Authentication on any tenant:
Not sure it's worth keeping since it should not work on any tenant. |
Repo updated to remove the |
Hello,
I recently found out the the o365 module uses the autodiscover login (https://autodiscover-s.outlook.com) with BasicAuth to do the spraying. Recently, Microsoft have block Basic Auth authentication on all tenant (see https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online).
Is there plans to change the login method used by the module to fix this ?
Thanks
The text was updated successfully, but these errors were encountered: