Skip to main content

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to Cloud.

Other available versions:

Versions 6 and 7Link: What version am I on?

Code42 Support

Configure Azure for SSO in your Code42 environment

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to Cloud.

Other available versions:

Versions 6 and 7Link: What version am I on?

Overview

To configure your Code42 environment to use Azure AD for single sign-on (SSO), you must create a new enterprise application in Azure. This tutorial explains how to create the application in Azure and how to configure your Code42 cloud environment to use Azure AD for SSO. For more information about how Code42 implements SSO, see our introduction to single sign-on.

If you use Active Directory Federation Services (AD FS) for SSO on an Azure instance, see  Configure Microsoft AD FS for SSO in your Code42 cloud environment.

Considerations

  • Code42 usernames must match SSO usernames. How you accomplish this depends on how you deploy Code42 apps.
  • Code42 supports service provider-initiated SSO but does not support identity provider-initiated SSO. Therefore, users cannot sign in to your Code42 environment from the identity provider's website or application, but instead must log in using a browser bookmark. 
  • SSO provides user authentication but does not provide user management. Set up SCIM provisioning or use the Code42 administration console to manage users. 
  • To configure Code42 to support advanced SAML request configurations using the Code42 API, see Use the Code42 API to set SAML attributes
External authentication systems
Our Customer Champions can help with authentication issues caused by interaction with Code42 products. However, troubleshooting authentication issues outside your Code42 environment is beyond the scope of our Customer Champions. For assistance with external authentication systems, contact your authentication vendor.

Before you begin

Verify identity provider configuration
  • Make sure the SSL certificate of your SSO identity provider has been signed by a trusted Certificate Authority (CA).
  • Make sure you have administrative access to the identity provider or have contact with an identity provider administrator.
Verify network configuration
  • Configure your private network, Internet, and VPN settings to allow client devices to communicate with your identity provider on ports 80 and 443. Test client connectivity to the identity provider before you proceed.
  • If you want to use URL-based metadata exchange to configure Code42 and the identity provider to work together, make sure two-way communication is available between them on TCP ports 80 and 443. If two-way communication is not available or not allowed, you must download the identity provider's metadata file and make it accessible to Code42.
  • Confirm the required ports with your identity provider to determine if custom ports are being used.

Step 1: Register an app in Azure

  1. Sign in to your Azure portal
  2. Go to Azure Active Directory.
  3. Select Overview.
  4. Click App Registration.
    Azure screen showing how to select "App registration".
  5. Enter a name for the new application in the Name field of the Register an application panel.
  6. For Supported account types, select Accounts in this organization directory only (Default Directory only - Single tenant).
  7. For Redirect URI, select Web and enter the URL for your Code42 environment:
  8. Click Register.
    Azure screen showing how to register an application.

Step 2: Expose an API for the app registration in Azure

  1. In the app registration you created in Step 1, select Expose an API.
  2. Next to Application ID URI, click Set.
    Azure screen showing how to set an application ID URI.
  3. In the Application ID URI field, enter the URL for your Code42 environment:
  4. Click Save. 
  5. Make any other settings changes your app registration requires and add users to the new application. 
    See Microsoft's documentation for more information on configuring app registration settings in Azure.
    Azure screen showing how to set the "Application ID URI".

Step 3: Copy your Azure federation metadata URL

  1. In the app registration you created in Step 1, select Overview.
  2. Click Endpoints.
    Azure screen showing how to select Endpoints.
  3. Copy the Federation metadata document. You will enter this in the Code42 administration console. 
    Azure screen showing how to copy the Federation metadata document.

Step 4: Add Azure to your Code42 administration console

  1. Sign in to the Code42 administration console.
  2. Navigate to Administration > Settings > Identity Management.
    Authentication Provider screen
  3. Click Add Authentication Provider.
    Add Authentication Provider dialog
  4. In Display Name, enter an identity provider name to display to users who sign in with SSO.
    If your Code42 environment provides more than one SSO identity provider, users see a list of providers to choose from. They must select the provider configured for their Code42 organization.
  5. In Provider's Metadata, ensure that Enter URL is selected and paste the federation metadata URL you copied in Step 3.
  6. Click Create Provider.
    Authentication provider settings appear.
    Authentication provider details
Apply provider to organizations in later steps
This provider will not be applied to an organization until you update the organization security settings. Do not apply this authentication provider to organizations yet. You will apply this provider to a test organization and to production organizations in later steps.

Step 5: Configure attribute mapping

  1. Next to Attribute Mapping, click the Edit icon. Edit_icon.png
  2. Deselect Use default mapping.
  3. Configure attribute mapping:
    1. Username: Select Use attribute tag and enter: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
    2. Emailhttp://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
    3. First Namehttp://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
    4. Last Namehttp://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname
  4. Click Save.

Step 6: Test SSO authentication

  1. Create a test user in your identity provider. 
  2. Sign in to the Code42 administration console.
  3. Create a test organization.
  4. Configure the test organization to use SSO.
    1. Navigate to Organizations, then select the organization.
    2. From the action menu in the upper-right, select Edit.
    3. Click Security.
      Security tab
    4. Deselect Inherit security settings from parent.
    5. From Select an authentication method, choose SSO.
      The configured SSO identity providers appear.
    6. Select the identity providers that you want to offer for the organization.
    7. From Select a directory service, select Local.
    8. Click Save.
    9. Type ENABLE in the field provided and click ENABLE.
  5. Create a user in the test organization who matches the identity provider test user.
  6. In the upper-right of the administration console, select Account > Sign Out.
  7. Sign back in to the administration console as the test user to verify that SSO is working.

Step 7: Apply to additional organizations

Enable SSO for one or more organizations in your Code42 environment. If two or more authentication providers are offered in your Code42 environment, tell the users in each organization which authentication provider they should choose when they sign in.

Option A: Enable SSO for a specific organization

  1. Sign in to the administration console.
  2. Navigate to Organizations, then select the organization.
  3. From the action menu, select Edit.
  4. Click Security.
    Security tab
  5. Deselect Inherit security settings from parent.
    Disabled inheritance
    If you disable inheritance for an organization, that organization is not affected by changes to its parent organization.
  6. From Select an authentication method, choose SSO.
    The configured authentication providers appear.
  7. Select the identity providers that you want to offer for the organization.
  8. From Select a directory service, select Local.
  9. Click Save.

Option B: Enable SSO for all organizations

Modify the system-wide organization settings to enable SSO for all organizations.

  1. Sign in to the administration console.
  2. Go to Organizations > Active.
    Parent organization hierarchy
  3. Click on the top-level organization.
    The organization details appear.
  4. From the action menu, select Edit.
  5. Click Security.
    Apply provider to parent organization
  6. From Select an authentication method, choose SSO.
    The configured authentication providers appear.
  7. Select the identity providers that you want to offer to your organizations.
  8. From Select a directory service, select Local.
  9. Click Save.
  10. Under each child organization, make sure that Inherit security settings from parent is enabled.
    1. Click the child organization.
    2. From the action menu, select Edit.
    3. Click Security.
    4. Enable Inherit security settings from parent.

Step 8: Add new users who sign in with SSO

Option A: Add users in the administration console

Use the administration console to add users to an organization that uses SSO.

  • Verify that the users in the organization exist in the SSO identity provider used by the organization.
  • Make sure that the Code42 environment usernames match the SSO usernames.

Option B: Deploy the Code42 app

New users can register accounts in your Code42 environment:

  1. Distribute the Code42 app installer to new users
  2. Choose Sign up for an account when you open the Code42 app.
  3. Create an account using the SSO credentials. The Code42 app username must match the SSO username.

What to expect

Reduced authentication prompts

When a user signs in with SSO, the user does not need to re-enter credentials for subsequent authentication attempts until the SAML authentication token expires. A SAML token applies to an application rather than a device, which means that a user might need to enter credentials again when signing into a different app. Signing in to the Code42 app does not authenticate the administration console because one is an app on the device and the other is accessed via a web browser.

Losing access to an identity provider

If a user loses access to the identity provider, the Code42 app continues to back up, uninterrupted.

  • Was this article helpful?