Automatically provision, update and deprovision users in Druva from JumpCloud using the Identity Management (SCIM) integration. Leverage this integration to centralize user lifecycle, user identity, and group management in JumpCloud for Druva. Save time and avoid mistakes, as well as potential security risks, related to manually creating users.
Read this article to learn how to setup the Druva integration.
Prerequisites
- A JumpCloud Administrator account
- A Druva user account with administrator permissions – only Druva Cloud administrators and inSync Cloud administrators can generate a token.
- A Druva enterprise SaaS app.
Important Considerations
- Druva SCIM API is based on version 2.0 of the SCIM standard.
- If you need to update your token, you must deactivate the IdM integration, update the token, and then reactivate the IdM integration.
- Deactivation or deletion of a user in the IdP leads to the preservation of the user account in Druva inSync.
- inSync does not create, update, or delete any user accounts or modify their information.
- Users preserved by administrator in the inSync Management Console, cannot be re-activated from the IdP.
- If a user is deactivated from IdP, administrators need to again assign the SCIM app to the user to activate (change user account status from Preserved to Active) the user account in inSync.
- The SCIM attributes that you define in the SCIM mapping must be mapped to the IdP attributes in the IdP; else the user creation fails.
- If a user does not classify or fall under any SCIM mapping created in Druva inSync, the user account creation fails.
- Druva recommends that you also create a default mapping with the configuration ‘Allow any user’. This default mapping will ensure that any users who do not classify or fall under any of the mappings are created with a default configuration. The priority of this default mapping can be set to lowest.
- Once you create a SCIM mapping, you can only modify the Mapping Name and inSync configuration. You cannot modify the Users criteria to filter users.
- The option to use SCIM is available only to customers who have not used AD or LDAP to manage users in inSync.
- No AD or LDAP account must be configured to import users in inSync Management Console.
- No AD or LDAP mapping should exist in inSync Management Console.
- No AD or LDAP managed user in ‘Active’ and ‘Preserved’ state should exist in the inSync Management Console.
- The profile and storage assigned to the manually added users in inSync and which you may want to manage using SCIM, stay the same even after the migration.
- The filter is case sensitive. The value you specify in the SCIM mapping and the attribute value in IdP should be in the same case.
- The Token is valid for 365 days from the day it is generated.
- In Druva, The following operations are supported for users:
- Create users.
- Deactivate or Remove users.
- Update users.
- In Druva, The following updates to user information are supported:
- Display Name
- Email address
- Status
- In Druva, The following SCIM provisioning actions are not supported:
- Password sync.
- Managing or migration of user accounts from inSync to IdPs.
- Managing of user groups within IdPs in inSync.
Attribute Considerations
- A default set of attributes are managed for users. See the Attribute Mappings section for more details.
Creating a new JumpCloud Application Integration
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Click + Add New Application.
- Type the name of the application in the Search field and select it.
- Click Next.
- In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.
- If this is a Bookmark application, enter its URL in the Bookmark URL field.
- Click Save Application.
- If successful, click:
- Configure Application and go to the next section.
- Close to configure your new connector at a later time.
Configuring the SSO Integration
To configure JumpCloud
- Create a new application or select it from the Configured Applications list.
- Select the SSO tab.
- Replace any instances of YOUR_SUBDOMAIN with the name of your subdomain.
- Add any other desired attributes.
- Click activate, then continue.
- Click Download Certificate when the Public Certificate has been created message appears.
The certificate.pem will download to your local Downloads folder.
To configure Druva
- Click the hamburger menu to access the Global Navigation Panel > Druva Cloud Settings > Access Settings. The Access Settings window appears.
- In the Single Sign-On section, click Edit.
- Enter the following information:
- IdP URL: Paste the IDP URL from Jumpcloud Admin Console.
- IdP Certificate: Paste the Public Certificate downloaded in the previous section.
- Click Save.
- In the Single Sign On section, press on the Generate the SSO Token option.
- Make a copy of your Insync Auth Token.
- Click Save.
To configure JumpCloud 2
- Back in the SSO tab, enter insync_auth_token=Insync_Auth_Token where Insync_Auth_Token matches to Insync Auth Token from the SSO Configuration on Druva side.
- Click Save.
Authorizing User SSO Access
Users are implicitly denied access to applications. After you connect an application to JumpCloud, you need to authorize user access to that application. You can authorize user access from the Application Configuration panel or from the Groups Configuration panel.
To authorize user access from the Application Configuration panel
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
- Select the User Groups tab. If you need to create a new group of users, see Get Started: Groups.
- Select the check box next to the group of users you want to give access.
- Click save.
To learn how to authorize user access from the Groups Configuration panel, see Authorize Users to an SSO Application.
Validating SSO authentication workflow(s)
IdP Initiated
- Access the JumpCloud User Console.
- Select the Service Provider icon.
- This should automatically launch and login to the application.
SP Initiated
- Navigate to your Service Provider application URL.
- You will be redirected to log in to the JumpCloud User Portal.
- The browser will be redirected back to the application and be automatically logged in.
Configuring the Identity Management Integration
To configure Druva
- On the inSync Management Console menu bar, navigate to Users > Deployment.
- In the Select a user provisioning method window, click Use SCIM and click Confirm.
- If you have not been redirected already, click the Settings tab
- In the Auth Token for SCIM section, click Generate Token.
- Copy the token for the next section.
The token is not stored in Druva
To configure JumpCloud
- Create a new application or select it from the Configured Applications list.
- Select the Identity Management tab.
- Click Configure.
- You’re presented with two fields:
- Base URL: Enter the SCIM URL for Druva:
- If you are inSync Cloud Customer: https://apis.druva.com/insync/scim
- If you are inSync GovCloud Customer: https://govcloudapis.druva.com/insync/scim
- Token Key: Paste the SCIM API Key you generated/copied when configuring Druva.
- Click activate and then click save.
- You will receive a confirmation that the Identity Management integration has been successfully verified.
- You can now connect user groups to the application in JumpCloud to provision the members of that group in Druva. Learn how to Authorize Users to an Application.
Attribute Mappings
The following table lists attributes that JumpCloud sends to the application. See Attribute Considerations for more information regarding attribute mapping considerations.
Learn about JumpCloud Properties and how they work with system users in our API.
Druva User Attributes
JumpCloud Property | JumpCloud UI Field Name | SCIM v2 Mapping | Druva Value |
---|---|---|---|
username | Username | userName | Email address |
active | Status | active | active |
employeeIdentifier | Employee ID | externalId | externalId |
displayname | Display Name | displayName | displayName |
Removing the Integration
To deactivate the IdM Integration
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to deactivate and click to open its details panel.
- Under the company name and logo on the left hand panel, click the Deactivate IdM connection link.
- Click confirm.
- If successful, you will receive a confirmation message.
To deactivate the SSO Integration
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to deactivate and click to open its details panel.
- Select the SSO tab.
- Scroll to the bottom of the configuration.
- Click Deactivate SSO.
- Click save.
- If successful, you will receive a confirmation message.
To delete the application
- Log in to the JumpCloud Admin Portal.
- Go to USER AUTHENTICATION > SSO Applications.
- Search for the application that you’d like to delete and click to open its details panel.
- Check the box for the application.
- Click Delete.
- Enter the number of the applications you are deleting
- Click Delete Application.
- If successful, you will see an application deletion confirmation notification.