Open brynwhyman opened 4 years ago
I thought this would have been partly possible by at least only limiting the MFA flow to users who have some sort of access to the CMS, but apparently that's not the case.
I'm tracking down more information on this.
Overview
We've heard from project teams that adding MFA to some sites is blocked if the project includes members that do not have access to the CMS.
In these cases, Site Owners would like the MFA flow to only apply to certain users that have some level of access to the CMS.
A common example is where member profiles are being used to store customer login details for a separate portal managed within the site.
Options
In both of these options, if a user has already registered MFA for their account, they will continue using MFA each time they log in regardless of MFA settings.
Regardless of which option we select, we have to decide:
Option 1: If you're not in the group, you can't register MFA for your account
This is the behaviour of the existing PR.
Option 2: Groups only apply for making MFA required
This was suggested (and designed for) in https://github.com/silverstripe/silverstripe-mfa/pull/409#issuecomment-725774762 but later rejected in favour of option 1
PRs