Use Okta as your identity provider so users sign in to Dispel with their Okta credentials over OAuth (OIDC) or SAML.
Connect Okta — Okta's enterprise identity platform — as your organization's identity provider. Once connected, your users sign in to Dispel with their Okta credentials through single sign-on. You can connect Okta over OAuth (OIDC) or SAML.
This page covers the Okta-specific setup. For the shared behavior that applies to every provider — how users sign in, group mapping, MFA, and disconnecting — see Identity Providers.
You'll configure the IdP side in the Okta Admin Console, so you'll need administrative access there.
Decide on a protocol — OAuth (OIDC) or SAML. See Choosing a protocol.
Make sure the users who will sign in via Okta are already invited to your organization in Dispel. SSO authenticates users but doesn't create access on its own.
In the Okta Admin Console, go to Applications → Create App Integration and choose OIDC — OpenID Connect.
Set the sign-in redirect URI to your Dispel address followed by /oauth/login-callback — for example https://app.dispel.com/oauth/login-callback. Confirm the exact address for your environment with your Dispel representative if you're unsure.
Assign the app to the users or groups who should have access.
Click Connect on the Okta card and Select Authentication Protocol → OAuth.
Fill in the fields:
Click Save settings.
In the Okta Admin Console, go to Applications → Create App Integration and choose SAML 2.0.
In the SAML settings, paste the values Dispel shows at the top of its SAML form:
Single sign-on URL / Recipient / Destination ← Dispel's Assertion Consumer Service URL.
Audience URI (SP Entity ID) ← Dispel's Service Provider (SP) Entity ID
Click Connect on the Okta card and Select Authentication Protocol → SAML.
Copy the Service Provider (SP) Entity ID and Assertion Consumer Service URL shown at the top of the form (use Copy ID / Copy URL) into Okta, as above.
Fill in the fields:
Click Save settings.
Click Test connection. Dispel redirects you to Okta to sign in, then shows the email and name it received. If the test fails, confirm the values match your Okta app and that the test user is invited to your organization.
Users sign in by entering your Organization Identifier on the Dispel sign-in screen and authenticating with Okta. See .
Map Okta groups to Dispel groups so membership stays in sync — see .
MFA enforced in Okta applies during sign-in; Dispel's email one-time codes don't apply to SSO users. See .
To switch protocols or providers, disconnect first. See .
From the app's General tab, copy the Client ID and Client secret, and note your Okta domain / issuer.
Finish creating the app, then open its Sign On tab and collect:
Identity Provider Single Sign-On URL → Dispel's SSO URL.
Identity Provider Issuer → Dispel's Identity Provider Entity ID.
The X.509 / signing certificate → Dispel's Base64 Signing Certificate.
Assign the app to the users or groups who should have access.
Client URL
Your Okta OAuth/OIDC endpoint (issuer), e.g. https://your-org.okta.com.
Client ID
The application's Client ID.
Client Secret
The application's Client secret.
Organization Identifier
A unique identifier you choose; users type it on the sign-in screen.
SSO URL
The Identity Provider Single Sign-On URL.
Identity Provider Entity ID
The Identity Provider Issuer.
Base64 Signing Certificate
The Okta signing certificate. Paste it or use Upload Certificate.
Organization Identifier
A unique identifier you choose; users type it on the sign-in screen.