Can JumpCloud integrate with my organization’s identity source of truth? What about our HRIS solution?
We hear this type of question more and more from small and medium enterprise (SME) IT admins. The question is not surprising, given that the SME segment is the fastest growing segment in the global HR market: SMEs accounted for over 60% of that market share in 2020, according to Verified Market Research.
Being able to answer “yes” when someone asks us whether JumpCloud can integrate with their identity source and HRIS platform is vital — particularly because user identity management now affects both IT and HR. As a shared concern, it is increasingly important to ensure there are efficient, consistent, and, whenever possible, automated identity lifecycle management processes between these two departments, regardless of the HR and IT solutions in place.
With the latest updates to the JumpCloud identity management custom API connector, the answer to “Can JumpCloud integrate with my identity source or HRIS solution?” is increasingly “yes.”
What is the JumpCloud Identity Management Custom API connector?
The JumpCloud custom API connector provides an open and flexible way to integrate JumpCloud with a broad number of identity sources. This includes HRIS, human capital management (HCM), compensation, and benefits platforms, as well as other cloud directories. JumpCloud can integrate with many leading HR solutions, like ADP, BambooHR, and Workday, as well as many other HRIS and non-HRIS solutions.
How Does It Work?
From the JumpCloud Admin Portal, an IT admin completes a configuration template that defines the authentication method, API endpoints, and the attribute mappings needed to create the integration between JumpCloud and the application serving as the identity source. Once that configuration is verified, the integration is activated and available to use to import user identities directly into JumpCloud from the identity source, connecting the HR and IT worlds.
User Identity Lifecycle (Co-)Management
HR and IT have always shared the objective of high employee satisfaction and productivity from onboarding to offboarding. How each department achieved this objective used to be distinct, with minimal overlap of responsibilities and concern.
Now, however, identity management is a collaborative effort between HR and IT. HR assumes the responsibility of creating and keeping the person’s identity current, as well as triggering onboarding and offboarding flows. IT is more focused on assigning and maintaining the appropriate access and permissions throughout the user’s lifecycle. This includes access to all the resources a person needs to be productive during their entire tenure with the organization, as well as deprovisioning the user’s identity and access when they leave.
This shift in responsibilities has created the need for information to flow from an organization’s identity source to JumpCloud. In the past, JumpCloud has offered integrations and automations from JumpCloud to applications. Now, JumpCloud is using the same types of integrations and automations to transmit information from identity sources to JumpCloud. This allows JumpCloud to act as a pass-through of the user identity information.
However, many of these identity sources do not have integrations to JumpCloud. Without an integration, both IT and HR must perform multiple manual, insecure, error-prone processes. These processes have the potential to negatively impact employees’ ability to do their jobs and create security vulnerabilities.
To fill this gap, JumpCloud offers several options for integrating with these identity sources in the JumpCloud Admin Portal. The solutions range from specific integrations built by JumpCloud (such as Personio, Workday, Google Workspace, and M365) to open solutions: the custom SCIM connector and the custom API connector. All of these options support employee onboarding (joiners).
In addition, we have added support for keeping a user’s profile in-sync as changes are made in the identity source (movers) and for deprovisioning identities when a user’s status is set to inactive in the identity source (leavers).
With each addition to our open and flexible integration options, our answer to the question of whether JumpCloud integrates with an organization’s chosen identity source gets closer and closer to a universal “yes.”
Explore the Integration Options
To explore JumpCloud’s available integration options, go to the JumpCloud Admin Portal and navigate to Directory Integrations > HR Directories > +. If you don’t have a JumpCloud account, you can try it for free for up to 10 users and 10 devices by creating a JumpCloud Free account. Sign up to explore how JumpCloud enables you to make work happen — from anywhere, on any device, and with the platforms you choose. Make Work Happen™ on your terms.