Multiple Enterprise SSO Connections per Organization
Blog post from PropelAuth
PropelAuth now allows a single organization to connect multiple identity providers, enabling groups such as employees, contractors, or acquired teams to access the same workspace through separate Okta, Entra ID, Google Workspace, SAML, OIDC, and SCIM configurations. The opt-in feature is enabled at both project and organization levels, with each connection assigned email domains that automatically route users to the appropriate provider without requiring them to select a connection. Separate setup links let different customer teams configure only their own identity provider, while eligible customer administrators can maintain configurations, certificates, nicknames, and SCIM settings for connections matching their email domain. Developers using Enterprise SSO APIs gain an endpoint for listing connections, must provide connection IDs for certain SCIM group requests, and may need to include a domain or email address in direct login redirects to avoid ambiguity. Existing authorization logic, organization-scoped queries, and role checks remain unchanged, while new connections in multi-connection organizations must be created through setup links.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Platform Engineering | 3 | 1,191 | 259 | 79 | -17% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.