Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
2fa [2019_09_23 16:22] – created jim | 2fa [2024_02_28 01:03] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======Two-Factor Authentication (2FA)====== | + | # Two-Factor Authentication (2FA) |
- | The Enterprise File Fabric supports two-factor authentication. This can also be referred to as two-step verification or dual factor authentication. | + | #### last updated on: Feb 14, 2023 |
- | 2FA is a security process in which the user provides | + | Access Anywhere Server supports two-factor authentication (2FA). This is sometimes referred to as two-step verification, |
- | If 2FA is turned | + | 2FA is an additional security process in which a user provides two different authentication factors to verify themselves when logging in to better protect the resources the user can access. |
- | Two Factor Authentication | + | Note that 2FA is set at an account level so can be used to protect storage resources that do not support 2FA by default. |
- | The options for 2FA are: | + | 2FA can be configured for individual users (accounts) or at an organization level. |
- | |||
- | - Nominated password | ||
- | - Google Authenticator TOTP (also works with Microsoft Authenticator) | ||
- | Once turned on users will have to login as normal | + | ### External Users |
+ | |||
+ | Setting 2FA for an organization doesn' | ||
+ | |||
+ | |||
+ | ===== Organization Level Setup ===== | ||
+ | |||
+ | Two Factor Authentication can be turned on for all of a organization' | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | The protocol adapters [[clouddav|]] and [[cloudftp|]] do not support 2FA. You can optionally disable them from this page for further security. (For this option to be visible the Feature "2FA for API" must be enabled for the User Package.) | ||
+ | |||
+ | Three types of 2FA are supported. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | ====Email==== | ||
+ | |||
+ | ===How it Works=== | ||
+ | |||
+ | On each login attempt the user will have to enter a timed one-time password. | ||
+ | {{ : | ||
+ | The password will be emailed automatically to the email address associated with her Access Anywhere account. Each login requires a new one-time password. | ||
+ | |||
+ | ===Set-Up=== | ||
+ | |||
+ | The only set-up required is selecting this choice | ||
+ | |||
+ | ====Phrase==== | ||
+ | ===How it Works=== | ||
+ | When each user logs in for the first time after phrase based 2FA has been enabled, they will have establish a phrase to be entered on subsequent logins: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | On each subsequent login attempt the user will be challenged to enter the phrase: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | If an org. member forgets his phrase | ||
+ | |||
+ | ===Set-Up=== | ||
+ | |||
+ | As the org. admin you can both turn on phrase based 2FA for the org. and set up the phrase for your account. | ||
+ | |||
+ | ====Authenticator App (TOTP)==== | ||
+ | ===How it Works=== | ||
+ | On each login attempt the user will be have to enter a timed one-time password (TOTP) that has been generated by an app such as Google Authenticator on her phone. | ||
+ | |||
+ | |||
+ | {{ : | ||
+ | ===Set-Up=== | ||
+ | |||
+ | If the org. admin selects " | ||
+ | account will appear on the Security | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The QR code and the secret string are functionally equivalent. | ||
+ | |||
+ | On each user's first login after TOTP 2FA has been turned on, each user will have to download or save their own individual QR code or secret. | ||
+ | |||
+ | Android / iOS Apps that support TOTP include Google Authenticator, | ||
+ | |||
+ | =====Individual User Setup===== | ||
+ | |||
+ | If 2FA has not been activated for the organization then each user has the option of setting up 2FA for his/her own account. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | The choices, setup and use are the same as those described in the previous section. |