Ping Identity integrations

Ping Identity integrations

→

AFAS Profit → Ping Identity

AFAS to Ping Identity integration: employees from AFAS Profit as users in PingOne

→

Nmbrs → Ping Identity

Nmbrs to Ping Identity integration: users in PingOne from payroll

→

Workday → Ping Identity

Workday to Ping Identity integration: what PingOne's Workday provisioner does, and where custom work starts

→

Visma Raet YouForce → Ping Identity

YouForce to Ping Identity integration: Visma Raet as the HR source for users and groups in PingOne

→

HiBob → Ping Identity

HiBob to Ping Identity integration: employees from Bob as users in PingOne

→

Nedap ONS → Ping Identity

Nedap ONS to PingOne integration: care staff and teams as users and groups

Systems you can connect Ping Identity with

How KoppelHet connects to Ping Identity

PingOne provisioning syncs identities from a source into the PingOne directory (inbound) or from PingOne to target systems (outbound). For Workday the inbound provisioner checks for changes every 15 minutes. For importing identities Ping recommends the SCIM Users API.

Objects we connect

• Users in the PingOne directory
• Groups and populations
• Accounts in target applications

What a Ping Identity integration does

• Workday → to Ping Identity

  Workday as the source for PingOne

  With the Workday provisioner new and changed workers reach PingOne within 15 minutes.

  Workday → Ping Identity integrationIdentity and access management

• AFAS Profit, Visma Raet YouForce, Nmbrs → to Ping Identity

  Dutch HR source through SCIM

  Employees from AFAS, YouForce or Nmbrs go to PingOne through the SCIM Users API, with department, job and manager.

  AFAS Profit → Ping Identity integrationVisma Raet YouForce → Ping Identity integrationNmbrs → Ping Identity integrationIdentity and access management

• Ping Identity → to Slack, Atlassian Cloud (Jira en Confluence)

  Accounts in applications

  PingOne passes users to applications such as Slack and Atlassian Cloud with outbound provisioning.

  Slack integrationsAtlassian Cloud (Jira en Confluence) integrationsAccounts in applications

What to watch for

• Ping recommends the SCIM provisioning connection for outbound only. An HR integration that puts users into PingOne uses the SCIM Users 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