Configure InCommon for SSO in your CrashPlan environment

• CrashPlan app for Windows, Mac, and Linux
• CrashPlan console

• To use this functionality, you must be assigned the Identity Management Administrator role. 
• CrashPlan usernames must match SSO usernames. How you accomplish this depends on how you deploy CrashPlan apps.
• CrashPlan supports service provider-initiated SSO but does not support identity provider-initiated SSO. Therefore, users cannot sign in to your CrashPlan 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 CrashPlan console to manage users. 
• CrashPlan does not support Single Logout (SLO). Users must sign out of the identity provider to end their single sign-on session.
• The CrashPlan console expects SAML assertions to be signed. To configure CrashPlan to support advanced SAML request configurations, see Set SAML attributes for SSO in CrashPlan.

• 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.

• Configure your private network, Internet, and VPN settings to allow client devices to communicate with your identity provider on port 443. Test client connectivity to the identity provider before you proceed.
• If you want to use URL-based metadata exchange to configure CrashPlan and the identity provider to work together, make sure two-way communication is available between them on TCP port 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 CrashPlan.
• Confirm the required ports with your identity provider to determine if custom ports are being used.

Before you begin configuring SSO for CrashPlan, consider whether your company has more than one CrashPlan tenant that you need to connect to your SSO identity provider. Large companies and organizations often have separate, dedicated CrashPlan cloud instances (or "tenants") in use by different groups or departments. 

If you have more than one CrashPlan tenant to connect to your SSO identity provider, you need to obtain an entity ID URL for each CrashPlan tenant. An entity ID is a unique string that identifies a specific tenant to your SSO identity provider. The tenant-specific entity ID URL is composed of the CrashPlan domain followed by the tenant ID, and can be found in the CrashPlan service provider metadata URL file in each tenant. For example:

"entityId": "https://example.com/42424daa-424c-4e42-42c4-c424242420d4" 

1. Sign in to the CrashPlan console.
2. Navigate to Administration > Integrations > Identity Management.
   
3. Click Add Authentication Provider.
   
4. In Display Name, enter the federation name. 
5. In Provider's Metadata, ensure that Enter URL is selected and paste the URL. For the InCommon federation, use the IdP-only aggregate: https://mdq.incommon.org/entities/idps/all
   Use metadata URL for federations
   CrashPlan cloud environments do not support uploading an XML file for federations. Use the metadata URL to configure the federation instead. 
   Custom domains are not supported
   When entering the URL for the XML metadata file, custom domains are not supported. You must use the standard domain of your identity provider. 
6. Click Create Provider.
   CrashPlan automatically detects that the provider's metadata URL belongs to a federation, and details for the federation appear. 
   

1. From federation settings, Click Add an identity provider to this federation. 
   
2. Select a provider from the list.
   Begin typing to search the list.
3. Enter a display name for the provider to display to users who sign in. 
   If your CrashPlan environment provides more than one SSO identity provider, users see a list of providers to choose from. 
4. Click Add Identity Provider. 
   The provider appears under the federation.

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 CrashPlan console. 
3. Create a test organization.
4. Create a user in the test organization who matches the identity provider test user. 
5. Configure the test organization to use SSO:
   1. Navigate to Administration > Integrations > Identity Management.
   2. Select the authentication provider.
   3. Click Edit  next to Organizations in use.
   4. Select the test organization. 
      Note that you can also use an organization's settings to select an authentication provider to use for SSO.
   5. Click Save.
6. In the upper-right of the CrashPlan console, select Account  > Sign Out. 
7. Sign back in to the CrashPlan console as the test user to verify that SSO is working. 

1. Sign in to the CrashPlan console. 
2. Navigate to Administration > Integrations > Identity Management.
3. Select the authentication provider.
4. Click Edit  next to Organizations in use.
5. Select organizations to use the authentication provider for SSO.
   If applicable, select Inherits settings to identify whether an organization inherits the setting from its parent organization. To enable SSO for all organizations, select the top-most organization. (Note that you can also use an organization's settings to select an authentication provider to use for SSO.)
6. Click Save.