Identity and access management
Oracle HCM to JumpCloud integration: JumpCloud users from Oracle HCM Cloud, also where the JumpCloud import does not work
With an integration between Oracle HCM Cloud and JumpCloud, every employee from Oracle gets a JumpCloud user with employee number, job title, department, legal employer and manager, staged before the first working day and suspended after leaving. JumpCloud itself names Oracle HCM Cloud as a system that cannot use its own HR import; KoppelHet therefore writes directly through the JumpCloud API.
What the integration does
Organisations that have Oracle HCM Cloud as HR source and use JumpCloud for accounts, devices and SSO often look for an Oracle integration in JumpCloud and only find the app for Oracle Cloud Infrastructure. Users are then created by hand or with CSV files, and leavers stay active until someone remembers.
- In Oracle KoppelHet gets an integration user with read rights on workers and the employee Atom feeds.
- In JumpCloud the administrator creates an API key for an administrator account with only the rights the integration needs.
- At the start we link existing JumpCloud users to their PersonNumber, so nobody is created twice.
- A hire from Oracle becomes a staged user; on the start date KoppelHet sets the user to activated.
- On termination KoppelHet suspends the user on the last working day; for a cancelled hire it deletes the staged user.
What to watch for with Oracle HCM Cloud and JumpCloud
- In its own troubleshooting article JumpCloud lists Oracle HCM Cloud among the systems that the Custom API import currently does not work with. KoppelHet therefore does not try that import, but creates and changes the users itself through the JumpCloud API.
- The Oracle app in the JumpCloud catalogue is about Oracle Cloud Infrastructure. It handles SSO and pushes JumpCloud users into OCI through SCIM, the other way round. Fetching employees from Oracle HCM is not part of it.
- Oracle reports a hire as soon as it has a future start date. JumpCloud has the staged state, in which a user has no access to apps yet. KoppelHet creates the user in that state, so laptop and groups are ready, and activates the user on the first working day.
- If a candidate drops out before the start, Oracle sends a separate notification for the cancelled work relationship. Because the JumpCloud user was never active, KoppelHet deletes it, rather than leaving a suspended user for someone who never started.
- In JumpCloud employeeIdentifier is unique per user. KoppelHet puts the PersonNumber there, which stays the same on a transfer to another legal employer while Oracle creates a new work relationship. The colleague keeps their user, devices and MFA; only company and groups change.
- The manager field in JumpCloud points to another JumpCloud user, not to a number from Oracle. Oracle can have several managers per assignment; KoppelHet takes the line manager of the primary assignment, looks up their JumpCloud user and creates the manager first when both start at the same time.
- Oracle returns lists in pages of 25 items by default, with hasMore as the sign that there is more. In the nightly comparison KoppelHet reads on until hasMore is false, so a leaver on page twenty does not fall outside the check.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Can we not just use JumpCloud's HR import?
Not for Oracle HCM Cloud. JumpCloud itself names Oracle HCM Cloud as a system that import currently does not work with.
What happens to a leaver in JumpCloud?
The user is suspended on the last working day. Devices and history remain visible; deleting remains IT's choice.
Do contingent workers from Oracle get a user too?
You decide. The worker type is passed as employeeType, so groups in JumpCloud can treat contingent workers differently.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM Cloud: employee Atom feeds newhire (including future-dated hires), empassignment, termination and cancelworkrelship; workers resource with names, workRelationships (LegalEmployerName, PrimaryFlag), assignments (JobName, DepartmentName, LocationName) and managers; pagination with limit and offset, default 25, hasMore and totalResults=true.
- JumpCloud API v1 with the x-api-key header: POST and PUT /systemusers with username, email, firstname, lastname, employeeIdentifier (unique per user), jobTitle, department, company, location, employeeType, manager (id of another systemuser), attributes and state (STAGED, ACTIVATED, SUSPENDED); DELETE for a cancelled hire. Region URL console.eu.jumpcloud.com for an EU organisation.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in JumpCloud | Notes |
|---|---|---|
PersonNumber | employeeIdentifier | Unique per user in JumpCloud |
names (KnownAs of FirstName, LastName) | firstname, lastname | |
Naamgevingsregel | username en email | |
assignments: JobName | jobTitle | |
assignments: DepartmentName | department | |
workRelationships: LegalEmployerName | company | |
assignments: LocationName | location | |
WorkerType | employeeType | |
Lijnmanager van de primaire assignment | manager (JumpCloud-gebruikers-id) | |
Feeds newhire, termination en cancelworkrelship | state (STAGED, ACTIVATED, SUSPENDED) of verwijderen |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud