Previous Topic Next Topic

Multi-Factor Authentication (MFA)

ADSelfService Plus MFA augments the traditional username and password-based authentication with an additional layer of authentication (e.g. biometric or a OTP) to verify a user's identity. MFA provides a high level of identity assurance for access requests.

You can enable MFA in ADSelfService Plus for the following events:

• Self-service password reset and account unlock
• Endpoint logins (Windows, macOS, Linux, and VPN)
• Self-service portal login

To enable MFA for these events:

• First you need to configure the authentication methods.
• Then, go to the MFA for Reset/Unlock or MFA for Endpoints tab, and enable MFA for the required events.

Refer to the Authenticators page for the list of supported authentication methods, and how to configure them.

Combined with Conditional Access, MFA for Endpoints can be enabled only for high-risk users, thus ensuring security without affecting user experience. Click here to learn more about Conditional Access.

How to enable the required authentication methods for a specific set of users

1. Go to the Configuration > Self-Service > Policy Configuration, choose a policy of your choice, and click the Edit icon. You can also create a new policy by clicking the Add New Policy button.



2. Click Select OUs/Groups at the bottom right of the webpage, and select the specific set of users to whom you wish to enable multi-factor authentication. Click OK.
Tip:Select the Don't inherit child OU(s) option to only select the parent OUs.



3. Select the password self-service features (Reset Password, Unlock Account, Self Update, or Change Password) that you wish to enable for the selected users. Click Save Policy.



4. Go to the Configuration → Self-Service → Multi-Factor Authentication → Authenticator Setup and select a policy from the Choose the Policy drop-down.
5. Configure the authentication methods that you want to enable for the selected policy.



6. Click Save.
Tip: You can choose to configure different authentication methods for different sets of policies. For instance, if Policy 1 enforces YubiKey, Policy 2 can enforce one-time passcodes, and so on.

How to force users to enroll for specific authentication methods

Users must enroll themselves by providing the necessary information, as per the enabled authentication methods, to be able to prove their identity. For example, if you have enabled Fingerprint Authentication, users must scan their fingerprint using the ADSelfService Plus mobile app, only after which, they will be able to use that method during password reset or endpoint logins.

To force users to enroll for specific authentication methods:

1. Go to Configuration → Self-Service → Multi-factor Authentication → MFA Enrollment.
2. Select Force users to enroll when they log in to the end-user portal option. This will prevent users from accessing other features in the self-service portal before entering their enrollment information.
3. Select Enforce these authenticators during enrollment and choose the authenticators to be set as mandatory.





4. You can also choose to hide the Enrollment tab in the end-user portal for enrolled users
5. Click Save Settings.

What are the authenticators and functions supported by the various MFA types

This table provides detailed information on each MFA type, including the supported authenticators and the settings and options available to improve the functionality and security of the authentication process.

What are the authenticators supported by the ADSelfService Plus mobile app and mobile browser portal?

ADSelfService Plus offers 20 types of authenticators. Of these, eight basic authenticators are available with every edition of ADSelfService Plus. The other 12 are advanced authenticators, available only with the Professional edition of ADSelfService Plus.

This table provides detailed information on the basic and advanced authenticators supported for MFA in the ADSelfService Plus mobile app and mobile browser portal along with provisions for authenticator enrollment in the two consoles.

* - Users do not have to enroll for these methods because they are automatically enrolled upon logging in the first time.
+ - These authenticators are native to the mobile app and cannot be used in the mobile browser portal.

Previous Topic Next Topic