
IsaacB.81593 (Customer) asked a question.
Can a user still authenticate with a "disabled" authenticator in OIE?
In Classic, if a user was subject to an MFA enrollment policy that "disabled" a specific authenticator, such as SMS, they could not use it for MFA, even if they had it enrolled on their account. So, if a user was enrolled for SMS and I disabled SMS on the MFA enrollment policy that applied to them, they could not use that SMS to MFA.
In Identity Engine, it appears to me that if a user is enrolled in SMS and I disable SMS in the enrollment policy that they are subject to, they can continue to use SMS until I either revoke it from their account or disable SMS for the org at large.
Am I looking at this behavior correctly?
Thanks

Hello @IsaacB.81593 (Customer) Thank you for posting on our Community page!
You are asking whether Identity Engine lets a user keep using an SMS factor they already enrolled, even after you disable SMS in the MFA enrollment policy that applies to them, which differs from Classic Engine behavior.
Your reading is correct. In Identity Engine, the MFA enrollment policy controls which authenticators a user can newly enroll and whether enrollment is required. It does not revoke or block an authenticator the user has already enrolled. Sign-in challenges are governed by the authentication policy and the organization-wide status of each authenticator, so an enrolled SMS factor remains usable until you remove the enrollment from the user or disable SMS for the entire org.
Root Cause: Identity Engine separates enrollment (MFA enrollment policy) from verification (authentication policy plus org-level authenticator status). Classic Engine let the enrollment policy also block use of already-enrolled factors, which is why the behavior differs.
Solution: To stop a specific user from using SMS while keeping the org-wide setting, use one of the following:
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Thank you, Paul.
> Remove the existing SMS enrollment from the affected user in the Admin Console user profile,
> under Security → Multifactor, or with the Okta API factor lifecycle endpoints.
Did you mean "More Actions > Reset Authenticators?"
Hello @IsaacB.81593 (Customer) Thank you for that observation, in this case from "More Actions > Reset Authenticators?" will not be an option as that will reset all MFA from the user, unless this is something that you want to do.
In this case I would recommend to do this from API's where you can delete just one MFA
Call the Okta API to delete only the SMS factor.
First, send a GET request to /api/v1/users/{userId}/factors to find the SMS factor ID, then send a DELETE request to /api/v1/users/{userId}/factors/{factorId}.
This removes only that factor and leaves the user's other enrolled factors in place.