I've been managing a setup where we allow users who haven't enrolled in an MFA method to bypass it. The REQUIRE_USER_MATCH key has been set to FALSE and everything was running smoothly for several months. However, today I noticed a sudden issue. While regular MFA users are logging in without problems, users without MFA methods are now being rejected. In the event logs, I see two entries: one showing access was accepted earlier today but later in the afternoon access was rejected for the same user, indicating that no default authentication method is configured. I've tried repairing the extension and even uninstalled and reinstalled it. Has anyone faced this issue recently?
2 Answers
Have you confirmed that you’re using the correct version of the extension? I had similar issues once and just updating it did the trick. Also, if you've not already, try rebooting your server after these changes; it might help refresh everything.
First off, make sure your Azure MFA Extension is updated to the latest version. Double-checking that the registry key is set to false is also crucial. Don't forget to restart the NPS service every time you change something—it can make a difference.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures