Use case: Perform identity proofing with a third-party service

Summary

Problem: For additional verification of an end user's identity, use a third-party identity proofing service to confirm information from a driver's license, a photograph, or other types of documentation. Because of the typically custom nature of these flows, they are built on Okta hooks and APIs using either custom code or Okta Workflows.

Solution: During registration or at other stages in an end user's lifecycle, Workflows uses a third-party identity proofing vendor to start or retrieve the status of a user verification then log that information in the user's profile

Example Applications: Evident ID and OnFido. For the full list of available Workflows connectors, see Connectors.

Sample Flow 1

User is created >

Create user in identity proofing vendor API endpoint >

Receive verification from identity proofing vendor >

Update user profile or group(s)

Sample Flow 2

Scheduled flow >

Poll identity proofing vendor >

Update user profile or group(s)

Guidelines and limitations

Workflows system-wide limits apply. See Learn about Workflows best practices and limits.