Integration type
SIS (Student Info System)
What we solve
Oracle Student Cloud institutions need a low-code way to verify student identity at IAL2 and enforce step-up for sensitive actions (enrollment changes, financial aid approvals/disbursements) without building and maintaining custom integrations across Oracle services. This integration uses an Oracle Integration Cloud (OIC) adapter to trigger 1Kosmos IDV from student-enrollment events and write results back via callbacks, and federates 1Kosmos with Oracle IDCS via OIDC (acr_values /assurance/ial/2/) so Oracle policies can require higher assurance before permitting access or approving financial transactions.
Integration architecture
Oracle Student Cloud uses the Oracle REST API framework, authenticated via OAuth 2.0. The Oracle Integration Cloud (OIC) is the recommended iPaaS for connecting external services.
Touchpoint 1 — Oracle Integration Cloud adapter 1Kosmos publishes an Oracle OIC adapter that registers as a connection type within OIC. Institutions drag-and-drop the adapter into OIC integration flows:
Touchpoint 2 — Oracle IDCS federation Oracle Student uses Oracle IDCS as its identity provider. 1Kosmos federates with IDCS via OIDC, enabling step-up challenges to be routed through the existing identity fabric:
Touchpoint 3 — Financial aid step-up Oracle Financial Aid Cloud disbursement actions are gated by Oracle Approval Management. 1Kosmos IAL2 verification can be inserted as an approval rule condition:
Integration complexity: High
Oracle OIC is powerful but expensive to operate. Institutions need Oracle Integration Cloud licensing on top of Oracle Student Cloud. The OIC adapter path reduces custom development to near-zero once the adapter is published.
