For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs.
Skip to content

Okta

Use Okta as your identity provider so users sign in to Dispel with their Okta credentials over OAuth (OIDC) or SAML.

Overview

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.

Where to find it. Sign in as an organization administrator and open Settings → Integrations (or the dedicated Settings → Authentication page). Okta appears in the Identity & Authentication (IdP / SSO) section. Click Connect on its card to begin.

Before you begin

  • 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.

Connect with OAuth (OIDC)

In Okta

  1. In the Okta Admin Console, go to Applications → Create App Integration and choose OIDC — OpenID Connect.

  2. 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.

  3. Assign the app to the users or groups who should have access.

  4. From the app's General tab, copy the Client ID and Client secret, and note your Okta domain / issuer.

In Dispel

  1. Click Connect on the Okta card and Select Authentication Protocol → OAuth.

  2. Fill in the fields:

Field
Value from Okta

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.

  1. Click Save settings.

Connect with SAML

In Okta

  1. In the Okta Admin Console, go to Applications → Create App Integration and choose SAML 2.0.

  2. 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.

  3. 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.

  4. Assign the app to the users or groups who should have access.

In Dispel

  1. Click Connect on the Okta card and Select Authentication Protocol → SAML.

  2. 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.

  3. Fill in the fields:

Field
Value from Okta

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.

  1. Click Save settings.

  2. 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.

After connecting

Frequently asked questions

Which protocol should I use with Okta?

Either works. Use whichever matches the app you create in Okta — an OIDC app integration for OAuth, or a SAML 2.0 app integration for SAML.

Do I need to assign users to the Okta app?

Yes. Only users (or groups) assigned to the Okta app can authenticate through it. They must also be invited to your Dispel organization.

My SAML test connection failed. What should I check?

Confirm the SSO URL, Issuer, and certificate match your Okta app's Sign On settings, that you pasted Dispel's SP Entity ID and ACS URL into Okta's SAML settings, and that the test user is assigned to the Okta app and invited to your Dispel organization.

Last updated

Was this helpful?