Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
public:emai:zimbra_2fa [2021-03-02 15:49] – vesely | public:emai:zimbra_2fa [2021-03-26 11:01] – vesely | ||
---|---|---|---|
Line 3: | Line 3: | ||
Two-factor authentication is a technology that provides identification of users with the combination of two different components. | Two-factor authentication is a technology that provides identification of users with the combination of two different components. | ||
- | As the 2nd factor is used the smartphone app - **Google Authenticator **{{: | + | As the 2nd factor is used the smartphone app - **Google Authenticator **{{: |
===== General ===== | ===== General ===== | ||
Line 60: | Line 60: | ||
If the user now goes to another Web Browser, computer, smartphone, or if he or she tries to configure Zimbra Desktop, the user will successfully pass the two-factory authentication. For example on the Web Client: One-time Codes | If the user now goes to another Web Browser, computer, smartphone, or if he or she tries to configure Zimbra Desktop, the user will successfully pass the two-factory authentication. For example on the Web Client: One-time Codes | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== One-Time Codes ===== | ||
+ | |||
+ | With the two-factor authentication enabled, there may be a situation when the smartphone doesn’t have battery to answer the code challenge, or the device has been lost, etc. For cases like this, Zimbra introduces the One-time codes functionality. This function allow users to generate multiple codes to use in case of emergency. The total number of one-time codes can be configured by the Admin. | ||
+ | |||
+ | The user can click on the One-time codes View option to see the codes. The user must keep the codes secure (written somewhere, in another device, etc.). | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== How to revoke trusted computer/ | ||
+ | |||
+ | Once the user trust some computer/ | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Application Passcode (IMAP, ActiveSync) ===== | ||
+ | |||
+ | Clients such as IMAP or ActiveSync do not support the UI flow needed for TOTP authentication. For these users need to generate application passcode. | ||
+ | |||
+ | ==== Application passcodes ==== | ||
+ | |||
+ | * Randomly generated. | ||
+ | * Can be created by giving a label and revoked by their label. | ||
+ | * Changing account password will revoke all application passcodes. | ||
+ | |||
+ | ==== How to create an application passcode ==== | ||
+ | |||
+ | User can create an application passcode by navigating to Preferences > Accounts > Applications and selecting Add Application Code button. User can enter the application name in the Add Application Code dialog and click Next. Application passcode will get generated and it can be used to sign in to your account. | ||
+ | |||
+ | <font inherit/ | ||
+ | |||
+ | The appplication passcode serves as a password once it is accepted by Zimbra during initialization procedure. | ||
+ | |||
+ | **You must make the __first time__ | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ==== How to revoke an application passcode ==== | ||
+ | |||
+ | Once the user generates application passcode user can revoke it by navigating to Preferences > Accounts > Applications in Zimbra Web Client. User can revoke this application passcode after selecting the required name in the list. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Failed Login Attempts ===== | ||
+ | |||
+ | Please note, use of Two-Factor Authentication (2FA) does not prevent account suspension due to exceeding failed login attempts limits | ||