Understanding how SSO works with User Provisioning and Syncing

Single sign-on (SSO) is a technology that combines several different application login screens into one. With Simpplr, there are four ways we can implement single sign-on with different SSO service providers.

  1. SSO with JIT (Just in Time) provisioning with CSV for people data syncing. Example: ADFS and SFTP for de-provisioning and people data syncing. 
  2.  SSO with file-based provisioning and de-provisioning and people data syncing with SFTP tool. (ADFS, SFTP CSV).
  3. SSO with the same source for provisioning and de-provisioning with People data syncing (examples: Okta, Google, Azure, OneLogin).
  4. SSO with different provisioning and de-provisioning source and People syncing data. Example: (PingOne for SSO and Google for provisioning and de-provisioning and People data syncing)
  5. SSO with the same source for provisioning and de-provisioning and different Source People data syncing (example: Azure for SSO for provisioning and de-provisioning AND Active Directory for people data syncing or Okta for provisioning and de-provisioning and CSV for people data).

The diagram below explains how user provisioning and syncing work in conjunction with your SSO.


This next diagram shows People data mapping with the SSO provider as the source.



Finally, this diagram shows the flow of using your SSO provider only for SSO, then using a CSV file to provision and sync users.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.

Articles in this section

See more