JumpCloud User provisioning
Provision and de-provision users in Currents using JumpCloud
Last updated
Provision and de-provision users in Currents using JumpCloud
Last updated
Create users - JIT provisioning when they first login to Currents.
Update user attributes - accept name updates for users.
Deactivate users - prevents the user from logging into Currents, deactivated users are removed from the Currents team member list.
Import users - Link your existing Currents users to their JumpCloud user.
For more information on the listed features, visit the .
Provisioning is available for customers with an active subscription.
In order to setup provisioning you first need to:
Setup the SAML integration with JumpCloud
Reach out to the Currents support team to have provisioning enabled for your organization.
Login as an Admin and navigate to the Manage Team page.
Click the Show SCIMv2 Details button in the DOMAIN ACCESS & SSO section of the page.
Note the Endpoint and Token details for JumpCloud Configuration
Navigate to the existing Currents SSO Application in JumpCloud USER AUTHENTICATION > SSO Applications. Click on the Currents SSO Application you previously setup.
Select the Identity Management tab. Then provide the Base URL (Endpoint) and API Token information from Currents. Also enter a Test User Email that does not already exist in Currents.
Click Test Connection and verify it was successful.
If everything was succeful, click Save
Navigate to the Current SSO App again, and back into the Identity Management Tab
Use the manual import button to find your existing Currents accounts
The Currents User Provisioning does not support the following JumpCloud Identity Management features:
Group Management
Sync password
Currents does not accept updates to the following attributes:
userType - changing a user's role is only supported from the Currents team member dashboard
userName - the mapped userName must match the primary email
email - the primary email cannot be changed
JumpCloud attempts to use the first part of the email as the username when importing new users from Currents. (eg, andrew@currents.dev becomes andrew )
If your users have a + character in their email, the import will fail. To workaround, first create the user in JumpCloud, then sync them with Currents. JumpCloud and Currents will sync based on the user email.
Toggle off Group Management and click Activate to verify the .
Your existing users should have been auto-matched based on email. If there are any additional Currents users that failed to be matched, you can import them from the import screen. (See )
When setting up Identify Management in JumpCloud, you must use a new user as the test email, otherwise you get errors during the test. This is referenced in .
