02-02-2023 08:12 AM
Hello JumpCloud Community! My name is Sam Morgan. I am a Principal Product Manager on our Directory team here at JumpCloud. My primary focus is our HR and Cloud Directory integrations. Until just recently, my focus included all user provisioning integrations, integrations that provisioned users to and from JumpCloud. This is my first community post.
We just released some exciting changes to our custom API integration capabilities. IT Administrators can now keep user data, in JumpCloud, in sync with the user data in the application to which a custom API import integration has been created. With the click of a button in the Admin Portal, or a single API call, an IT Administrator can import new active users, update existing user data, and deprovision (automatically suspend) users in JumpCloud based on the user data pulled from the source application. Previously, only new users could be imported.
The Why: As an open directory platform, JumpCloud accepts user identities from anywhere. We hear from IT Administrators that one of their biggest challenges is keeping those identities accurate throughout the user lifecycle (joiner, mover, leaver). This is especially true now that more Small and Medium Enterprise (SME) organizations are adopting cloud-based solutions for people management and other HR functions.
The purpose of the custom API import integration option is to provide IT Administrators with a more automated way to keep user data accurate, from their organization’s source of truth, if an integration with JumpCloud doesn’t already exist. This source could be an HR solution, a compensation solution, another cloud directory, or any other application with a REST API.
By keeping the user data accurate throughout the entire lifecycle, the IT Administrator can more effectively keep a user’s access and permissions right. The outcomes are a more secure user identity, efficiencies for the IT (and HR), and a positive experience for the end user.
Capability evolution: Getting to this point has been a journey.
Technical details: To use the custom API import integration option, the source application must meet the following criteria:
Roadmap: We aren’t done yet. There is more we intend to do with our custom API integration capability.
Learn more: To learn more about our custom API integration capabilities, take a look at our support article, Import users from an external identity source using a custom API integration and our Create an import job API documentation. We also have a blog post on this topic, JumpCloud Expands Open Integration Options to More Identity Sources.
To learn more about how this fits into Advanced Identity Lifecycle Management, join me for IT Hour on Friday, February 3rd.
New to the site? Take a look at these additional resources:
Ready to join us? You can register here.