Connections
A connection is a source of identities. Which connection a user comes from determines how they authenticate, which fields CSI Auth owns, and what can be changed through the API.
Connection types
Database connections
Credentials are stored in Auth0. CSI Auth owns the password policy and the user record.
Social connections
Identities come from a consumer provider such as Google or Apple. The provider owns the credential; CSI Auth stores the linked profile.
Enterprise connections
Identities come from a partner or corporate directory over SAML or OIDC. The directory owns the credential, the profile, and often group membership.
Choosing a connection
How connections are managed
Connections are provisioned through Terraform rather than through the API or the dashboard. The management API exposes reads only, so use it to inspect configuration rather than to change it.
Enabling a connection for an app
A connection has to be enabled per client before users from it can sign in to that app.
Attribute mapping
Enterprise connections map directory attributes onto the CSI Auth profile.
Account linking
A person who signs in through two connections gets two user records unless the accounts are linked.
Onboarding a new enterprise connection
- Collect the partner’s metadata and required claims
- Provision the connection in the sandbox tenant
- Test with a partner-supplied account
- Promote through the environments
- Enable it for the applications that need it