Okta integrations

Okta integrations

→

AFAS Profit → Okta

AFAS to Okta integration: AFAS Profit as the HR source for all accounts and apps

→

Workday → Okta

Workday to Okta integration: identities from HR, with your own rules for the Netherlands

→

Visma Raet YouForce → Okta

YouForce to Okta integration: Visma Raet as the HR source for Okta users and groups

→

HiBob → Okta

HiBob to Okta integration: Okta users from Bob, with the HiBob integration or custom

→

HR2day → Okta

HR2day to Okta integration: HR2day as the HR source for Okta

→

Nedap ONS → Okta

Nedap ONS to Okta integration: care staff and teams as the source for Okta

Systems you can connect Okta with

How KoppelHet connects to Okta

Okta Management API (Users and Groups), the Identity Sources API for a custom HR source (Anything-as-a-Source), or Okta as a SCIM target through inbound SCIM.

Authentication: OAuth 2.0 service app of API-token

Objects we connect

• Users and profile attributes
• Groups
• Lifecycle status (STAGED, ACTIVE, DEPROVISIONED)

What a Okta integration does

• AFAS Profit, Visma Raet YouForce → to Okta

  Dutch HR system as a source in Okta

  The integration delivers the employees from AFAS and YouForce through the Identity Sources API, so Okta treats them as a source.

  AFAS Profit → Okta integrationVisma Raet YouForce → Okta integrationIdentity and access management

• Workday → to Okta

  Workday with its own rules for the Netherlands

  Workday workers become Okta users with profile attributes. Dutch employees follow their own rules, such as the start date on which a user moves from STAGED to ACTIVE.

  Workday → Okta integrationIdentity and access management

• Dayforce, AFAS Profit → to Okta

  Deprovisioning after leaving

  An end date in HR sets the user to DEPROVISIONED after the last working day, which revokes access to all connected apps in Okta.

  Dayforce → Okta integrationAFAS Profit → Okta integrationIdentity and access management

What to watch for

• Dutch HR systems such as AFAS and YouForce connect through the Identity Sources API.

In your IT landscape

• Runs as a managed integration on the KoppelHet platform, next to your existing integration layer. No VPN into your network.
• Only the fields in the design you approve are transferred. The platform keeps no register of its own.
• Tested first in the test or acceptance environment where there is one. You choose the go-live moment.
• ISO 27001 certified, hosted in Amsterdam. When the contract ends you receive the configuration and the audit logs.

Implementation, architecture and compliance

Processes with this system

• Identity and access management

Topics that involve Okta

• Application provisioning
• SCIM and SCIM Gateway
• Collaboration and password management