multi-router.aidocs

Single Sign-On

OktaEnterprise

Creating the Multi-Router app in Okta and connecting it to Multi-Router.

Okta connects to Multi-Router as an OpenID Connect web app. The app in Okta gives Multi-Router a client ID and client secret, and Okta's assignments decide which people can sign in. This page covers the Okta side; the Multi-Router side is on Setting Up SSO.

Creating the app in Okta

  1. In the Okta Admin Console, open Applications, then Applications, and select Create App Integration.
  2. Choose OIDC - OpenID Connect as the sign-in method and Web Application as the application type.
  3. Name the app, such as Multi-Router, and set Grant type to Authorization Code.
  4. Set Sign-in redirect URIs to https://dashboard.multi-router.ai/sso/callback.
  5. Under Assignments, choose who can use the app, such as a group of engineers, and save.
  6. Copy the Client ID and Client secret from the app's General tab.

Choosing the issuer

The issuer is the Okta authorization server that signs the app's tokens. Okta offers two, and the Issuer / Discovery URL in Multi-Router must match the one the app uses exactly:

Authorization serverIssuer
Default custom authorization serverhttps://example.okta.com/oauth2/default
Org authorization serverhttps://example.okta.com

The org authorization server is available on every Okta org, and the default custom server on orgs with API Access Management. Opening the issuer followed by /.well-known/openid-configuration in a browser shows its discovery document, and its issuer value, exactly as written, is the one to enter.

Connecting it to Multi-Router

On the Single Sign-On (SSO) page in Multi-Router:

  1. Choose Okta as the Identity provider and enter the company's email domain.
  2. Enter the issuer as the Issuer / Discovery URL, and the app's Client ID and Client secret.
  3. Choose New-user access and the organization, select Test connection, then Set up SSO.
  4. Verify the domain with the DNS TXT record the page shows.
  5. From a private browser window, sign in with an Okta user who is assigned to the app.

Assignments and access

Okta lets only assigned people sign in to the app, so assignments are the first control on who reaches Multi-Router. With Auto-provision, an assigned person is added to Multi-Router on their first sign-in. With Invite-only, they also need an invitation. Removing an assignment stops new SSO sign-ins, and with Require SSO on, every new sign-in; sessions already open end when they expire. To create and remove people in Multi-Router from Okta directly, connect user provisioning. See User Provisioning (SCIM).

Setting Up SSOMicrosoft Entra ID
Was this helpful?