Single Sign-On
OverviewEnterprise
Signing in to Multi-Router through your company's identity provider with OpenID Connect.
Single sign-on (SSO) lets people sign in to Multi-Router with their company account from the organization's identity provider, such as Okta, in place of a separate Multi-Router password. The identity provider decides who can sign in, so access follows the company's own controls, such as multi-factor authentication. With Require SSO turned on, the identity provider is the only way in, so a person removed there can no longer sign in once their session ends. SSO covers both the dashboard and the Portal.
How it works
Multi-Router connects to the identity provider over OpenID Connect. Each SSO connection belongs to the account and is tied to one email domain, such as example.com, that the company proves it owns. A sign-in follows these steps:
- The person enters their work email on the Multi-Router sign-in page.
- Multi-Router recognizes the email domain and shows Continue with SSO.
- The person signs in at the identity provider, which sends them back to Multi-Router.
- Multi-Router checks the identity provider's response and signs the person in to the organization the connection provisions into.
Parts of a connection
An SSO connection has these parts, each set on the Single Sign-On (SSO) page in Account Settings:
| Part | Purpose |
|---|---|
| Identity provider | The company identity provider, such as Okta. |
| Email domain | The domain whose people sign in through SSO, verified with a DNS record. |
| Connection details | The identity provider's issuer URL, and the client ID and client secret of the Multi-Router app created there. |
| New-user access | Whether people the identity provider signs in are added automatically, or only people already invited. |
| Default role and organization | The role new people receive, and the organization they are added to. |
| Require SSO | Whether password and social sign-in are turned off for the domain. |
SSO and user provisioning
SSO signs people in; user provisioning with SCIM creates, updates and deactivates people in Multi-Router from the identity provider ahead of their first sign-in. SCIM builds on SSO: turning on user provisioning needs an SSO connection, and while provisioning is connected, the directory decides who has access. See User Provisioning (SCIM).
Related topics
The other pages in Single Sign-On cover each step in detail:
| Page | Covers |
|---|---|
| Setting Up SSO | Every field, domain verification, testing and saving. |
| Okta | Creating the Multi-Router app in Okta and connecting it. |
| Microsoft Entra ID | Registering Multi-Router in Entra ID. |
| Google Workspace | Creating an OAuth client in Google Cloud. |
| Ping Identity | Creating an OIDC web app in PingOne. |
| JumpCloud | Creating a custom OIDC application in JumpCloud. |
| Other OpenID Connect Providers | Connecting any OpenID Connect provider. |
| Signing In | What people see, first sign-in, and sessions. |
| Requiring SSO | Turning off password and social sign-in for the domain. |
| Troubleshooting | Sign-in and setup errors, with causes and fixes. |