Federated Authentication and SSO
Sign in to Streamkap with a magic link, Google, GitHub, Microsoft, or Slack, or connect an enterprise identity provider over SAML 2.0 or OpenID Connect.
Streamkap supports enterprise Single Sign-On (SSO) allowing your organization to use your existing identity provider for authentication.
Supported Authentication Methods
- Magic Link (Passwordless email authentication)
- GitHub
- Microsoft
- Slack
- Enterprise SSO (SAML 2.0 and OpenID Connect)
Enterprise SSO
For organizations requiring centralized identity management, Streamkap supports:
- SAML IDP Setup - For SAML 2.0 compliant identity providers
- OpenID Connect - IDP Setup - For OIDC compliant providers
SSO with Sub-Accounts
When using SSO across multiple sub-accounts, the SAML Entity ID (also called the SP Entity ID or SAML Identifier) is shared by default across your root account and all sub-accounts. This works fine in most cases, but some identity providers require a unique identifier for each enterprise application.
If you encounter issues such as:
- Your IdP (e.g., Microsoft Entra / Azure AD) rejects duplicate identifiers when creating separate enterprise applications per sub-account
- SSO authentication fails because the IdP cannot distinguish between sub-accounts sharing the same Entity ID
- You need independent SSO configurations per sub-account with different role mappings or group assignments
Then you may need unique Entity IDs assigned to each sub-account.
To request this, contact Streamkap support. Unique Entity IDs will be assigned following a naming convention like:
| Account | Entity ID |
|---|---|
| Root Account | Streamkap-SSO (unchanged) |
| Sub-Account A | Streamkap-SSO-{sub-account-name-a} |
| Sub-Account B | Streamkap-SSO-{sub-account-name-b} |
Once assigned, you can create separate enterprise applications in your IdP for each sub-account, each using its corresponding Entity ID.
Setup Guide
For detailed instructions on configuring SSO, see Setup SSO.