Skip to main content

Who is this article for?
Find your product plan in the Code42 console on the Account menu.

Incydr Professional and Enterprise
Incydr Basic and Advanced
Other product plans

Incydr Professional and Enterprise, yes.

Incydr Basic and Advanced, yes.

CrashPlan Cloud, yes.

Other product plans, yes.

CrashPlan for Small Business, no.

This article applies to Code42 cloud environments.

Other available versions:

On-premises

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Two-factor authentication for local users

Who is this article for?
Find your product plan in the Code42 console on the Account menu.

Incydr Professional and Enterprise
Incydr Basic and Advanced
Other product plans

Incydr Professional and Enterprise, yes.

Incydr Basic and Advanced, yes.

CrashPlan Cloud, yes.

Other product plans, yes.

CrashPlan for Small Business, no.

This article applies to Code42 cloud environments.

Other available versions:

On-premises

Overview

Two-factor authentication for local users increases the security of your Code42 environment by requiring users who authenticate directly with Code42 to provide additional verification before accessing the Code42 console and Code42 API.

For organizations integrated with an external authentication provider, this typically only applies to a very limited number of administrator accounts reserved for troubleshooting your authentication provider. However, if your organization only uses Local authentication, it applies to all users.

Before you begin

  • Review any Code42 API integrations using credentials of users in organizations in which you plan to enable local two-factor authentication. After enabling local two-factor authentication for an organization, basic authentication (username and password) is not supported. Users in that organization must use token authentication and supply the Time-based One-Time Password (TOTP) to authenticate with the Code42 API.
  • Review the organizational hierarchy of your Code42 environment. By default, child organizations inherit the local two-factor authentication setting from their parent organization. To prevent this setting from affecting unintended users, you can either move the users you want to use local two-factor authentication to an organization with no child organizations, or manually disable the setting in each child organization.

Considerations

  • Local two-factor authentication uses the Time-based One-Time Password (TOTP) algorithm and a 160-bit secret key for each user. The Google Authenticator mobile app is the tool we officially support and recommend, but other tools or apps that support the TOTP algorithm may also be compatible.
  • To configure this setting for an organization, you must sign in to the Code42 console as a user with the Customer Cloud Admin or Multi-Factor Auth Admin role.

Affected users and components

  • Users in organizations that only use local authentication
  • Dedicated local users in organizations with an external authentication provider
  • Code42 console access
  • Code42 API authentication

Unaffected users and components

  • Users in organizations that authenticate with an external authentication provider who are not specifically defined as a local user
  • The Code42 app installed on user devices
  • Any existing multi-factor authentication mechanisms managed by your external authentication provider

Enable or disable two-factor authentication

Incydr Professional and Enterprise

Incydr Basic and Advanced, CrashPlan Cloud, and other plans

User sign in

After enabling Local Two-Factor Authentication for an organization, affected users are required to follow the steps below to set up their account the next time they sign in. (Future sign-ins only prompt users to obtain the verification code from their authenticator.)

  1. Upon signing in to the Code42 console, the Set Up Two-Factor Authentication message appears.
  2.  Using your authenticator, scan the QR code provided (see sample below).
  3. (Optional) If you plan to script automated API requests with this account and/or integrate with other TOTP applications, copy the code from this message and save it.
  4. In the Enter 6-digit verification code field, enter the verification code displayed in your authenticator.
  5. Click Sign In

2FA-user-setup-prompt

Reset a single user's device

If a user loses or gets a new mobile device, follow the steps below to reset the two-factor authentication configuration.

  1. Sign in to the Code42 console.
  2. Select Administration > Environment > Users.
  3. Select a user.
  4. From the action menu in the upper-right, select Reset Two-Factor Authentication.
    This invalidates the secret used to generate this user's TOTP and prompts the user redo the initial configuration steps upon the next sign-in attempt.

External resources