Configure multi-factor authentication (MFA)

Updated at:

Multi-factor authentication (MFA) requires an end user to provide a second security factor — a dynamic password or a verification code — in addition to a username and password when the end user logs on.

How MFA works

After you enable MFA for an office network or for an organization, the system verifies two security factors each time an end user logs on:

  • First factor: The username and password of the end user.

  • Second factor: The dynamic password generated by a virtual MFA device, or the verification code that the end user receives in an SMS message or in an email.

Virtual MFA devices

The Time-based One-Time Password algorithm (TOTP) is a widely adopted multi-factor authentication protocol. Applications that support TOTP on a mobile phone or another device, such as the Alibaba Cloud app, Google Authenticator, and Microsoft Authenticator, are called virtual MFA devices.

After you enable MFA and an end user binds a virtual MFA device, Alibaba Cloud requires the end user to enter the six-digit dynamic password generated by the application at each logon. This prevents unauthorized logons that result from a stolen password.

Supported MFA methods

EDS Enterprise Edition supports the following MFA methods. The enablement scope that you choose determines which methods are available and which end users are affected.

Authentication method

Supported enablement scope

Supported client types

Supported account types

TOTP dynamic password

Organization ID and office network

No limit

No limit

SMS verification code

Organization ID

Windows client and macOS client (V7.6 or later); Android client and iOS client (V7.3 or later)

Convenience accounts and Active Directory (AD) accounts (a mobile phone number must be configured)

Email verification code

Organization ID

  • Windows and macOS clients (V7.6 or later)

  • Android and iOS clients (V7.3 or later)

Convenience accounts and Active Directory (AD) accounts (an email address must be configured)

Enable MFA for an office network

Enable MFA at this scope to require a dynamic password from the end users who use one specific office network to log on.

  1. Log on to the EDS enterprise console.

  2. In the left-side navigation pane, choose Networks & Storage > Office Network.

  3. In the top navigation bar, select a region.

  4. On the office network page, click the target office network ID.

  5. In the Other Information section at the bottom of the page, turn on the MFA switch, and then click OK in the confirmation dialog box.

    Note

    Make sure that client logon verification and the SSO settings are disabled.

    After MFA is enabled, end users must enter a dynamic password when they use this office network to log on to a terminal.

Enable MFA for an organization ID

Enable MFA at this scope to require a second security factor from every end user who uses the organization ID to log on.

  1. Log on to the EDS enterprise console.

  2. In the left-side navigation pane, choose Users > Logon Settings.

  3. On the Logon Security tab, set MFA to Enabled.

  4. In the confirmation dialog box, select the authentication method that you want to use.

    • TOTP

      End users enter the dynamic password generated by the Alibaba Cloud app or another common OTP app, such as Google Authenticator.

    • SMS Verification Code

      This method is available for convenience accounts and AD accounts on desktop clients V7.6 or later and mobile clients V7.3 or later.

      Note

      Users without a configured phone number cannot complete authentication.

    • Email Verification Code

      This feature is available for convenience accounts and AD accounts. It is supported only on desktop clients V7.6 or later and mobile clients V7.3 or later.

      Note

      Users without a configured mailbox cannot complete authentication.

After MFA is enabled, end users must enter the dynamic password or verification code that the selected authentication method requires when they use this organization ID to log on to a terminal.

Delete a virtual MFA device

End users bind a virtual MFA device the first time they log on after you enable MFA with TOTP dynamic passwords. If an end user replaces the virtual MFA device, delete the device that is bound to the account of the end user in the console.

Select the procedure that matches the account type of the end user.

Convenience account

  1. In the left-side navigation pane, choose Resources > Cloud Computers.

  2. In the left-side navigation pane, choose Users > Users.

  3. Find the target user, click the ⋮ icon in the Actions column. Then, select Manage MFA Device.

  4. In the Manage MFA Device dialog box, find the virtual MFA device that you want to delete, click Delete in the Actions column, and then click OK.

Enterprise AD account

Enterprise AD accounts in an office network

  1. In the left-side navigation pane, choose Resources > Cloud Computers.

  2. In the top navigation bar, select a region.

  3. Find the cloud computer assigned to the AD user, choose More > Manage MFA Device in the Actions column.

  4. On the Manage MFA Device panel, follow the on-screen instructions to delete the MFA device

Note

If you have enabled MFA for office network, the system locks a virtual MFA device for 1 hour if an end user who logs on to the terminal with an enterprise AD account enters an incorrect dynamic password more than 10 consecutive times. To allow the end user to log on during the lockout period, you can call the UnlockVirtualMFADevice API to unlock the device. Alternatively, you can call the DeleteVirtualMFADevice API to delete the device. If you delete the device, the end user must then attach a new virtual MFA device.

Enterprise AD accounts under an Organization ID

  1. In the left-side navigation pane, choose Resources > Cloud Computers.

  2. On the Logon Security tab, set MFA to Enabled.

  3. On the Logon Security tab, find the target AD account and click Manage MFA Device.

  4. In the Manage MFA Device panel, follow the prompts to delete the virtual MFA device.

After you delete the virtual MFA device, the end user must bind a virtual MFA device again at the next logon.