“Not required & not configured”

Hello @wbenterprises

Thank you for using our plugin.

For performance reasons, the user status is only checked and updated once the user logs in. So the plugin assigns a “default” status to users until they log in.

In builds prior to version 2.1.0, the default status was “Not required & not configured” which was clearly misleading. From version 2.1.0 onward, we have changed the default status to “User has not logged in yet, 2FA status is unknown”.

So it seems that you were using the plugin and have configured some policies prior to 2.1.0, hence why some users have the “Not required & not configured”. And most probably since we released 2.1.0 new users were created on the website, which now have the User has not logged in yet, 2FA status is unknown” status.

Can you please confirm if the above is correct?

Looking forward to hearing from you.

No, cannot confirm, but I noticed many users had this status even after logging in and accessing my content. They should not be able to do this without configuring 2FA. I am using 2.1, but I cannot identify when it was upgraded. Is there a log to see?

I set it to not require 2FA, then I set it back again, it seems to have relieved the issue, though. I will keep an eye on it closely for a few more days and report any new issues.

Thank you for the update @wbenterprises

I am glad to read that the issue has been “fixed”. I think this issue was caused during the upgrade. Let’s wait and see.

Let us know if you notice this again or if there is anything else we can help you with. Also, please do not forget to rate our plugin and service. These reviews really help us.