Skip to main content

Who is this article for?

Incydr Professional, Enterprise, Horizon, and Gov F2
Incydr Basic, Advanced, and Gov F1

Find your product plan in the Code42 console on the Account menu.
Not an Incydr customer? For CrashPlan articles, search or browse.

Instructor, no.

Incydr Professional, Enterprise, Horizon, and Gov F2, yes.

Incydr Basic, Advanced, and Gov F1, yes.

CrashPlan Cloud, no.

Retired product plans, no.

CrashPlan for Small Business, no.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Introduction to SCIM provisioning

Overview

SCIM provisioning allows you to automatically manage users in your cloud Code42 environment. Once enabled, Code42 creates new users, deactivates users, and updates user roles and permissions based on syncs with your provisioning provider. This article gives an overview of Code42 provisioning as well as some tutorials for configuring provisioning in the Code42 console. 

The SCIM provisioning feature is only available in cloud Code42 environments.

Definitions

What is SCIM provisioning?

SCIM provisioning is one way to manage users in your company. There are multiple ways to manage users in an IT system or application. For example: 

  • Manually: You can manually create, update, and deactivate users in every application each time a change happens. This method is time consuming, and it is difficult to scale in larger environments. 
  • Active Directory, OpenDirectory, or LDAP: Directory services where one user directory acts as a source of truth. Administrators make updates to one directory and the changes are synced to other systems and applications. This automates user management, which saves you time, and can scale to large environments. However, these directory services have firewall rules that may make it difficult to integrate with cloud applications. Note these options are not available in cloud Code42 environments, but are available for on-premises Code42 environments.
  • SCIM provisioning: SCIM provisioning relies on a provisioning provider as a source of truth. The provisioning provider may even connect to Active Directory, OpenDirectory, or LDAP on the back end. However, SCIM provisioning leverages REST and JSON to communicate, which makes it easier to integrate with cloud apps. It is also able to scale in large environments. 

How does SCIM provisioning work?

What it does

  • Performs actions to your Code42 environment based on the provisioning provider information:
  • Performs sync when a change occurs on the provisioning provider side. This means you must make a change on the provisioning provider to apply any updates to Code42. 

What it doesn't do

  • Code42 does not make any changes to your provisioning provider. Therefore, Code42 does not add, modify, or deactivate users in the provisioning provider.
  • Use LDAP. If your directory service requires LDAP to connect to Code42, use the Code42 User Directory Sync Tool. To configure the tool in your Code42 environment, contact your Customer Success Manager (CSM). 

Requirements

The Code42 provisioning feature requires you to connect a third-party provisioning provider to Code42. The following are the basic requirements that your provider and your Code42 environment need to integrate correctly:

  • Cloud Code42 environment: Provisioning is only available in cloud Code42 environments.
  • SCIM 2.0: Code42 requires a provisioning provider to use the SCIM 2.0 protocol. 
  • SCIM groups: The Custom SCIM mapping and role mapping require that your provider uses SCIM groups. Other provisioning features are available without SCIM groups. 

External resources

  • Was this article helpful?