Configure InCommon for SSO in your Code42 environment

The following Code42 components are compatible with SSO:

• Code42 agents for Windows, Mac, and Linux
• Code42 console

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

• 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 Code42 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 Code42.
• Confirm the required ports with your identity provider to determine if custom ports are being used.

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

If you have more than one Code42 tenant to connect to your SSO identity provider, you need to obtain an entity ID URL for each Code42 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 Code42 domain followed by the tenant ID, and can be found in the Code42 service provider metadata URL file in each tenant. For example:

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

1. Sign in to the Code42 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

6. Click Create Provider.
   Code42 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 Code42 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 Code42 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 Code42 console, select Account  > Sign Out. 
7. Sign back in to the Code42 console as the test user to verify that SSO is working. 

1. Sign in to the Code42 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 authtenication provider for SSO. 
   If applicable, select the 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.