- \n
- SCIM API Key<\/li>\n\n\n\n
- Bearer Token<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Does not require any special attribute mapping or extension schemas<\/li>\n<\/ul>\n\n\n\n
Important Considerations<\/strong><\/p>\n\n\n\n
- \n
- This integration is for provisioning, managing, and deprovisioning user identities and groups in other applications from JumpCloud<\/li>\n\n\n\n
- The custom SCIM integration option shown on the Identity Management tab for a specific application is not an indication that SCIM is supported.\u00a0The option allows you to test and determine\u00a0if an integration can be configured<\/li>\n\n\n\n
- The Test User Email must not exist<\/strong> in the application. <\/li>\n\n\n\n
- A test user and test group are created to test the integration. Both will be deleted if the DELETE method is supported by the service provider. If the DELETE method is not supported for users, then the test user will be deactivated and will have to be manually deleted if allowed by the service provider\n
- \n
- You provide a test user account to allow validation with applications that require verified domains for users<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- If you’re setting up a custom SCIM identity management connector for an application that isn’t already in the JumpCloud application catalog, please note the following:\n
- \n
- If the application doesn’t support or require SAML SSO, create a Bookmark<\/a> and add the custom integration to the bookmark<\/li>\n\n\n\n
- If the application does require a SAML SSO connection for their SCIM integrations, or SAML SSO is supported and you would like to implement it along with identity management, create a SAML 2.0 custom connector<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- User uniqueness is determined through a combination of ID, email, and username<\/li>\n\n\n\n
- Group syncing will only work if the Service Provider supports Group Creation, Group Updates, and Group Deletion. If a service provide only supports some of those actions, turn Off<\/strong> the Enable management of User Groups and Group Membership in this application<\/strong> option. Otherwise, the integration will fail with a group related error when you try to activate the integration<\/li>\n\n\n\n
- If a service provider does not support users being members of multiple groups, group membership syncing may fail if a user is a member of more than one group associated with the custom SCIM identity management integration<\/li>\n\n\n\n
- It there is already a connection between JumpCloud and the service provider for the user, we use the ID we have stored <\/li>\n\n\n\n
- If there is not already a connection for this user, we use their email to try to sync<\/li>\n\n\n\n
- If we aren’t able to get the user by email, we use their username <\/li>\n\n\n\n
- When checking by email and username we assert that there\u2019s only one (1) user, otherwise, we don\u2019t provision the user<\/li>\n<\/ul>\n\n\n\n
Attribute Considerations<\/strong><\/p>\n\n\n\n
- \n
- A default set of attributes are managed for users. See the Attribute Mappings<\/a> section for more details<\/li>\n\n\n\n
- For new integrations<\/strong>, sending passwords is disabled by default. Only enable this option if you are not using SSO or the service provider requires a password change and you are comfortable with your service provider’s handling of your sensitive information.<\/li>\n\n\n\n
- For integrations created before July 2022<\/strong>, sending passwords is enabled. This attribute should be checked and adjusted if this is not the desired setting<\/li>\n\n\n\n
- You can include, exclude, or change the default attribute mappings<\/li>\n\n\n\n
- Custom attributes and attributes not listed in the table below are not currently supported<\/li>\n\n\n\n
- The externalId <\/kbd>attribute is not sent from JumpCloud in the SCIM v2.0 implementation. If a service provider is using the externalId <\/kbd>attribute, the value they set is kept and respected. The externalId <\/kbd>is an optional attribute as outlined in the SCIM Core Schema definition. See the reference here<\/a><\/li>\n<\/ul>\n\n\n\n
Configuring a Custom SCIM Identity Management Connector <\/h2>\n\n\n\n
From here, there are many different ways to configure; through a pre-existing configured application, manually configure through a new SAML 2.0 connector or Bookmark. You can also configure through adding a new application connector or manually.<\/p>\n\n\n\n
- \n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to USER AUTHENTICATION<\/strong> > SSO<\/strong> Applications<\/strong>.<\/li>\n<\/ol>\n\n\n\n
To configure through an existing application, SAML 2.0 connector or Bookmark<\/strong><\/h3>\n\n\n\n
- \n
- Navigate to SSO Applications > Configured Applications<\/strong> and select an existing configured application that doesn\u2019t have a pre-built Identity Management integration (i.e., Abstract.) Then skip to Manually configure a Custom SCIM Identity Management Connector<\/a>.<\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\")
<\/p><\/div>Note:<\/strong> \nIf Identity Management<\/strong> is listed in the Supported Functionality<\/strong> column, the application already has a pre-built SCIM Identity Management integration built by JumpCloud. Find a connector without this to continue. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
To configure through a new application integration<\/strong><\/h3>\n\n\n\n
- \n
- Click + Add New Application<\/strong> to add a new application.<\/li>\n\n\n\n
- At the bottom of the page, click Custom SAML App<\/strong>. <\/li>\n\n\n\n
- Configure SAML SSO. Learn more in SSO Using Custom SAML Application Connectors<\/a>.<\/li>\n\n\n\n
- Next, skip to the section Manually configure a Custom SCIM Identity Management Connector<\/a>. <\/li>\n<\/ol>\n\n\n\n
To configure through a new Bookmark<\/strong><\/h3>\n\n\n\n
- \n
- Click + Add New Application<\/strong> to add a new application.<\/li>\n\n\n\n
- At the bottom of the page, click URL Bookmark<\/strong>.<\/li>\n\n\n\n
- Configure Bookmark, learn more about Connect Apps Using Bookmarks<\/a>.<\/li>\n\n\n\n
- Next, skip to the section Manually configure a Custom SCIM Identity Management Connector<\/a>. <\/li>\n<\/ol>\n\n\n\n
To configure through a new application connector<\/strong><\/h3>\n\n\n\n
- \n
- Click + Add New Application<\/strong> to add a new application, then click configure<\/strong> for the application that you would like to add Identity Management to.<\/li>\n<\/ol>\n\n\n\n<\/p><\/div>Note:<\/strong> \n
If Identity Management<\/strong> is listed in the Supported Functionality<\/strong> column, the application already has a pre-built SCIM Identity Management integration built by JumpCloud. Find a connector without this to continue. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Click the General Info<\/strong> tab and add a Display Label<\/strong>, Description<\/strong>, and replace the logo if this is a new application configuration.<\/li>\n\n\n\n
- Configure SAML SSO (Single Sign On) if the application service provider requires it to use SCIM for identity management.<\/li>\n<\/ol>\n\n\n\n
To manually configure a custom SCIM Identity Management Connector<\/strong><\/h3>\n\n\n\n
- \n
- Click the Identity Management<\/strong> tab.<\/li>\n\n\n\n
- Review the text at the top of Configuration Settings<\/strong> section regarding how the testing is done and any potential manual cleanup that may be required.<\/li>\n\n\n\n
- Select the\u00a0SCIM Version<\/strong>\u00a0and enter the service provider\u00a0Base URL<\/strong>\u00a0and\u00a0Token<\/strong>.<\/li>\n\n\n\n
- Enter a Test User Email<\/strong><\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\")
<\/p><\/div>Warning:<\/strong> \nThe Test User Email must not exist in the application. Using an existing email will cause the integration activation to fail.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Click test connection<\/strong>.<\/li>\n\n\n\n
- A connection to the service provider is attempted.\n
- \n
- You will receive one of the following notifications:\n
- \n
- Identity Management integration has been successfully verified. This will trigger a GET \/users request and a GET\/groups request sent to verify users and groups support by the service provider.<\/li>\n\n\n\n
- There was a problem activating Identity Management. This will trigger a detailed error message to appear. The response to the GET\/groups endpoint determines if groups are supported and whether the groups option or an error is shown in the Groups section.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- If groups aren’t supported by the service provider, you receive an error message.<\/li>\n\n\n\n
- If Group Management isn\u2019t supported by the service provider, you receive a message under the Group Management<\/strong> section saying, Group Management is not available for this service provider. {Error message. Group test failed}.<\/strong><\/li>\n<\/ol>\n\n\n\n<\/p><\/div>Note:<\/strong> \n
If the error message is longer than 200 characters, click learn more<\/strong> to open the modal with the full error message.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- If Group Management is supported by the service provider, you receive a message under the Group Managemen<\/strong>t section saying, This service supports groups. Select this to manage group and group membership in [your integration]<\/strong>.\n
- \n
- Leave Enable management of User Groups and Group Membership in this application<\/strong> option On<\/strong> to manage and sync groups and group members.<\/li>\n\n\n\n
- Slide the option to Off<\/strong> if you only want to manage user identities and not groups or group membership.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Click activate<\/strong>. <\/li>\n\n\n\n
- A change<\/strong>, update<\/strong>, and delete<\/strong> will be attempted for a test user. <\/li>\n\n\n\n
- If groups are supported, a change, update, and delete will be attempted for a test group.<\/li>\n\n\n\n
- If all tests pass without any errors, a confirmation notification will slide out from the right side of the window and there will be a Deactivate IdM Connection<\/strong> in the left panel under the Identity Management section.<\/li>\n\n\n\n
- If one or more errors occur:\n
- \n
- The error responses will be shown above the test and activate buttons, and the activate button will remain disabled. These errors will need to be reviewed and researched with the application service provider.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<\/p><\/div>Note:<\/strong> \n
If the error message is longer than 200 characters, click learn more<\/strong> to open the modal with the full error message. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- The Attribute Mapping<\/strong> section will appear above the test and activate buttons. This section allows you to map or exclude a subset of the SCIM core attributes if any of the errors are related to SCIM core attributes.<\/li>\n\n\n\n
- Once all errors have been addressed, click activate<\/strong>. <\/li>\n\n\n\n
- If all tests pass without any errors, a confirmation notification will slide out from the right side of the window and there will be a Deactivate IdM Connection<\/strong> in the left panel under the Identity Management section.<\/li>\n\n\n\n
- Your service provider should work with you to provide remediation options you can take to address the errors. <\/li>\n\n\n\n
- If there are custom attributes and schema extensions, the integration might not be possible with a custom integration. You can submit a feature request to have a pre-built connector created, if this is the case. From the top navigation bar of the Admin Portal, select Support<\/strong> > submit an idea<\/strong>.<\/li>\n<\/ol>\n\n\n\n
Attribute Mappings<\/strong><\/h2>\n\n\n\n
The following table lists attributes that JumpCloud sends to the application. See Attribute Considerations<\/a> for more information regarding attribute mapping considerations. <\/p>\n\n\n\n
Learn about JumpCloud Properties and how they work with system users in our API<\/a>. <\/p>\n\n\n\n
\nCustom SCIM User Attributes<\/h3>\n
\n \n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n JumpCloud UI <\/th>\n \n JumpCloud Attribute <\/th>\n \n SCIM Attribute <\/th>\n \n Notes <\/th>\n <\/tr>\n \n Company Email <\/td>\n \n email <\/td>\n \n userName <\/td>\n \n - <\/td>\n <\/tr>\n \n Company Email <\/td>\n \n email <\/td>\n \n emails.work <\/td>\n \n - <\/td>\n <\/tr>\n \n First Name <\/td>\n \n firstname <\/td>\n \n name.givenName <\/td>\n \n - <\/td>\n <\/tr>\n \n Middle Name <\/td>\n \n middlename <\/td>\n \n name.middleName <\/td>\n \n - <\/td>\n <\/tr>\n \n Last Name <\/td>\n \n lastname <\/td>\n \n name.familyName <\/td>\n \n - <\/td>\n <\/tr>\n \n Display Name <\/td>\n \n displayname <\/td>\n \n displayName <\/td>\n \n If Display Name isn't populated, we send 'First Name' + 'Last Name' <\/td>\n <\/tr>\n \n Work Address <\/td>\n \n addresses: type[=work] <\/td>\n \n addresses.type <\/td>\n \n We only send one address. Work is sent by default. If the work address is empty, then it's sent to the personal. If there aren't any addresses, we don't send this attribute. <\/td>\n <\/tr>\n \n Work Street Address <\/td>\n \n addresses: streetAddress <\/td>\n \n addressed.streetAddress <\/td>\n \n - <\/td>\n <\/tr>\n \n Work City <\/td>\n \n addresses: locality <\/td>\n \n addresses.locality <\/td>\n \n - <\/td>\n <\/tr>\n \n Work State <\/td>\n \n addresses: postalCode <\/td>\n \n addresses.region <\/td>\n \n - <\/td>\n <\/tr>\n \n Work Postal Code <\/td>\n \n addresses: postalCode <\/td>\n \n addresses.postalCode <\/td>\n \n - <\/td>\n <\/tr>\n \n Work Country <\/td>\n \n addresses: country <\/td>\n \n addresses.country <\/td>\n \n - <\/td>\n <\/tr>\n \n Work Phone <\/td>\n \n phoneNumbers: type [=work phone 'business'] phoneNumbers: number <\/td>\n \n phoneNumbers.[obj] <\/td>\n \n We only send one phone number. Work is sent by default. If the work phone if empty, then it's sent to the first personal phone number. If there aren't any phone numbers, we don't send this attribute. <\/td>\n <\/tr>\n \n Password <\/td>\n \n **password** <\/td>\n \n password <\/td>\n \n unhashed (send over secure communications channels). <\/td>\n <\/tr>\n \n activated <\/td>\n \n activated <\/td>\n \n active:true <\/td>\n \n - <\/td>\n <\/tr>\n \n suspended <\/td>\n \n suspended <\/td>\n \n active:false <\/td>\n \n - <\/td>\n <\/tr>\n \n Employee Type <\/td>\n \n employeeType <\/td>\n \n userType <\/td>\n \n - <\/td>\n <\/tr>\n \n Job Title <\/td>\n \n jobTitle <\/td>\n \n title <\/td>\n \n - <\/td>\n <\/tr>\n \n User Groups <\/td>\n \n - <\/td>\n \n groups:[obj] <\/td>\n \n We send all user groups that are associated with the application to which the user is a member. <\/td>\n <\/tr>\n \n Employee ID <\/td>\n \n employeeIdentifier <\/td>\n \n employeeNumber <\/td>\n \n - <\/td>\n <\/tr>\n \n Company <\/td>\n \n company <\/td>\n \n organization <\/td>\n \n - <\/td>\n <\/tr>\n \n Department <\/td>\n \n department <\/td>\n \n department <\/td>\n \n - <\/td>\n <\/tr>\n <\/table>\n<\/div><\/div>\n\n\n\n \nGroup Attributes<\/h3>\n
\n \n\n \n \n
- The error responses will be shown above the test and activate buttons, and the activate button will remain disabled. These errors will need to be reviewed and researched with the application service provider.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
- If Group Management is supported by the service provider, you receive a message under the Group Managemen<\/strong>t section saying, This service supports groups. Select this to manage group and group membership in [your integration]<\/strong>.\n
- You will receive one of the following notifications:\n
- Click + Add New Application<\/strong> to add a new application, then click configure<\/strong> for the application that you would like to add Identity Management to.<\/li>\n<\/ol>\n\n\n\n
- Navigate to SSO Applications > Configured Applications<\/strong> and select an existing configured application that doesn\u2019t have a pre-built Identity Management integration (i.e., Abstract.) Then skip to Manually configure a Custom SCIM Identity Management Connector<\/a>.<\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/tip-icon.png\"){kind=icon}
<\/p><\/div>![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/important-icon.png\"){kind=icon}
<\/p><\/div>