Integration type
HCM
What we solve
Oracle HCM Cloud customers need a way to verify new-hire identity and enroll biometrics during onboarding—since HCM captures PII but lacks built-in document/liveness verification—while also carrying that assurance into ongoing access policies. This integration uses Oracle Integration Cloud to trigger 1Kosmos BlockID Verify from New Hire Experience tasks, receive webhook completion events, and write verification status back to Oracle HCM via REST APIs; it can also update Oracle IDCS to enforce higher-assurance (IAL2) authentication after proofing is complete.
Platform identity landscape
Oracle HCM Cloud serves mid-to-large enterprises with a full lifecycle HR suite. Onboarding is managed through Oracle Talent Management Cloud with the New Hire Experience workflow. Oracle HCM uses Oracle Identity Cloud Service (IDCS) for authentication, which supports SAML and OIDC federation. The Oracle Integration Cloud (OIC) provides pre-built adapters for Oracle HCM REST APIs (/hcmRestApi/resources/11.13.18.05/workers, /newHires).
Oracle HCM has no native identity verification capability. The platform captures new hire PII through self-service forms but performs no document verification or biometric enrollment.
Technical integration architecture
Oracle IDCS federation note: BlockID AdminX can be registered as an external SAML/OIDC Identity Provider within Oracle IDCS. Once a worker's IAL2 proofing is confirmed, IDCS enforces that the worker's future authentications are serviced through BlockID, applying the registered biometric factor for all Oracle Cloud application access.
