Skip to main content

Who is this article for?

Incydr
Code42 for Enterprise
CrashPlan for Enterprise

Incydr, yes.

CrashPlan for Enterprise, yes.

Code42 for Enterprise, 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

Configure Google for SSO in your Code42 environment

Overview

This tutorial explains how to configure your Code42 cloud environment to use single sign-on (SSO) with Google. This article applies to environments in the Code42 cloud only. 

This article assumes you are already familiar with SSO and the SAML standard. For more information about how Code42 implements SSO, see our Introduction to single sign-on.

Compatible Code42 components

Compatible with SSO
  • Code42 app for Windows, Mac, and Linux
  • Code42 console
Incompatible with SSO
  • Code42 apps for iOS, Android, and Windows Phone

Considerations

Code42 supports service provider-initiated SSO but does not support identity provider-initiated SSO. Therefore, users cannot sign into your Code42 environment from the identity provider's website or application, but instead must log in using a browser bookmark. 

Contact support
Contact Code42 support for 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.

Before you begin

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.

Step 1: Add the SAML app in Google

Perform the following steps to set up a custom SAML app in Google to connect to Code42. For general information about setting up a custom SAML app, see Google's documentation.

  1. Sign in to the Google Admin console.
  2. Select Apps > SAML apps.
  3. Select Add app > Add custom SAML app.
  4. Enter an App name and click Continue.
  5. Click Download Metadata, save the file for use in Step 2 below, and click Continue.
  6. On the Service provider details page, complete the fields as follows.
    1. If you sign in to the Code42 console at https://www.crashplan.com/console, use:
      • ACS URLhttps://www.crashplan.com/api/SsoAuthLoginResponse 
      • Entity IDhttps://www.crashplan.com 
      • Start URLhttps://www.crashplan.com/login 
    2. If you sign in to the Code42 console at https://console.us.code42.com/console, use:
      • ACS URLhttps://sts-east.us.code42.com/api/SsoAuthLoginResponse 
      • Entity IDhttps://sts-east.us.code42.com 
      • Start URLhttps://console.us.code42.com 
    3. If you sign in to the Code42 console for the Ireland Code42 cloud at https://console.ie.code42.com/console, use: 
      • ACS URLhttps://sts-default.ie.code42.com/api/SsoAuthLoginResponse 
      • Entity IDhttps://sts-default.ie.code42.com 
      • Start URL: enter: https://console.ie.code42.com/console 
    4. If you sign in to the Code42 console for the Code42 federal environment at https://console.gov.code42.com/console, use:
      • ACS URLhttps://console.gov.code42.com/api/SsoAuthLoginResponse 
      • Entity IDhttps://console.gov.code42.com 
      • Start URLhttps://console.gov.code42.com/login 
  7. Leave Signed response unchecked and click Continue.
  8. On the Attributes page, click Add mapping and add the following mappings:
    • Primary email > uid
    • First name > givenName
    • Last name > sn
    • Primary email > mail
  9. Click Finish.
    Details of the SAML are displayed.
  10. Click User access and turn on the service for a test group.
    We recommend testing with a group first before turning on the service for all users. For more information, see Google's documentation.

Step 2: Add Google as an authentication provider

  1. Sign in to the Code42 console.
  2. Navigate to Administration > Integrations > Identity Management.
  3. Click Add Authentication Provider.
  4. In Display name, enter an identity provider name to display to users that 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, select Upload file, click Select a file, and select the metadata file you downloaded in Step 1.
  6. Click Create provider.
    Authentication provider settings appear.
    Authentication provider details
Provider information message

Note the following message on the dialog:
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.
  1. (Optional) Code42 recommends using the default settings. (They must match the mappings in Step 1 above.) But you can use Attribute mapping to customize additional mappings between Code42 platform user attributes and authentication provider SSO assertion attributes.
  2. (Optional) Local Users displays the current user. If there are any other users you want to exempt from using this authentication provider to log in, enter them here. 

Step 3: Test SSO authentication

To avoid impacting your production environment, use a test organization to verify that SSO is working properly. 

  1. Create a test user in your identity provider. 
  2. Sign in to the Code42 console.
  3. Create a test organization.
  4. Configure the test organization to use SSO.
    1. Navigate to Administration > Integrations > Organizations, then select the organization.
    2. From the action menu in the upper-right, select Edit.
    3. Click Security.
      Security tab
    4. Edit these settings in the Server section of the panel:
      1. Deselect Inherit security settings from parent.
      2. From Select an authentication method, choose SSO.
        The configured SSO identity providers appear.
      3. Select the identity providers that you want to offer for the organization.
      4. From Select a directory service, select Local.
    5. Click Save.
      The Enable Single Sign-on dialog appears.
      Enable SSO dialog
    6. Type ENABLE in the field provided and click ENABLE.
      The settings are saved to the organization. 
    7. To verify the settings, re-open the Security tab. Under Choose providers you should see the check box selected for your identity provider.
  5. Create a user in the test organization who matches the identity provider test user.
  6. In the upper-right of the Code42 console, select Account Account icon  > Sign Out.
  7. Sign back in to the Code42 console as the test user to verify that SSO is working.

Step 4: Apply this provider to production 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 Code42 console.
  2. Navigate to Administration > Environment > 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 Code42 console.
  2. Go to Administration > Environment > Organizations.
  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 5: Add new users who sign in with SSO

  1. Assign the custom SAML app to users or groups in the Google dashboard. See Google's documentation for more information.
  2. Ensure users are set up in Code42. You can add users manually with the Code42 console to an organization that uses SSO, or deploy Code42 apps to users in an organization that uses SSO. The users in Code42 must have first name, last name, and user name (email address) values that match the users' values in Google. 

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 Code42 console because one is an app on the device and the other is accessed via a web browser.

Lost access to an identity provider

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

Troubleshooting

Error: app_not_configured_for_user 

If a user attempts to sign in to Code42 and receives the Error: app_not_configured_for_user message, it may be due to one of the following problems.

  • The user is already authenticated in Google with a non-corporate account
    To resolve this issue, the user should sign in to Google using their corporate account, or log out completely from all Google accounts before signing in to their corporate account.
  • Incorrect application configuration
    To resolve this issue, verify that the service provider settings for the custom SAML app are configured correctly in the Google admin console.

For more failure types and solutions, see the Google documentation.

External resources

  • Was this article helpful?