Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

What is federated identity?
Federated Identity gives customers the option to use their own familiar company credentials to sign into CSI software and website instead of using their CSI sign-in credentials. To implement, the company will have to federate their identity platform (IdP) with CSI’s identity platform. Once setup, all contacts with federated email domains will automatically be redirected to their IdP for authentication.

Which identity platforms and standards does CSI support to setup federation?   

  • Microsoft Active Directory (Azure Active Directory, Active Directory, ADFS, AD/LDAP)
  • Google Workspace
  • OpenID Connect
  • Okta
  • PingFederate
  • SAML

Can customers who choose to setup federated identity still use the User Management Dashboard (UMD) to bulk import contacts to into the CSI database?
Yes, you can still import your your contacts in bulk using the UMD. When customers authenticate through federated IdP, they will be connected based on the user's email address. 

If a new user is authenticates via federated identity, how are they added to the CSI Database?
New users that authenticate via federated identity will be added on the fly to the default customer that is specified during federated identity setup. The new user will be giving assigned the customer's default role and added to the customer's default license group. The default role and default license group can both be found, and changed, in the User Management Dashboard.

Does CSI support SCIM Provisioning to keep a customer's IdP in sync with CSI's database? 
CSI currently does not support SCIM provisioning, but it is on the roadmap for early 2024.  


  • No labels