Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

SAML with Okta

Kindo has an application in the Okta Integration Network (OIN) catalog that configures SAML sign-in for you. You need to be an Okta administrator to add it, and an organization Admin in Kindo.

Before you configure Okta, create your organization’s SAML connection in Kindo under Settings → SSO. Follow Single Sign-On (SSO) Setup and keep the ACS URL and SP Entity ID available.

  • SP-initiated SSO: users start at the Kindo login screen.
  • IdP-initiated SSO: users start from the Kindo tile in Okta.
  • Just-in-time provisioning: Kindo creates an account on a user’s first sign-in when their email address uses your organization’s verified domain.

Add the Kindo app from the Okta catalog. If any of these apply, create a custom SAML app instead:

  • Searching the catalog for Kindo returns no app.
  • Your SP Entity ID in Kindo contains ?providerId=. The catalog app expects an SP Entity ID that ends in /sp/entity/<provider ID>.

The catalog app needs your Kindo SSO provider ID. Kindo shows it next to the SAML Connection heading in Settings → SSO. It’s also the last part of the ACS URL, after /sp/acs/. For example, in https://api.kindo.ai/auth/sso/saml2/sp/acs/saml-a1b2c3d4, the provider ID is saml-a1b2c3d4.

  1. In the Okta Admin Console, open Applications and Resources → Applications.

  2. Select Browse App Catalog.

  3. Search for Kindo, select the Kindo app, then select Add Integration.

  4. On General Settings, keep or change the Application label. Choose the app visibility settings your organization uses.

  5. Enter your Kindo SSO provider ID, then select Done.

  6. On the app’s Sign On tab, select Edit. Set Application username format to Email, then select Save.

    The email address must match the user’s Kindo email address on your organization’s verified domain.

The catalog app sends the email, givenName, and surname SAML attributes that Kindo reads, so you don’t add attribute statements.

Continue with Add the Okta details in Kindo.

Use a custom app when the catalog app doesn’t fit. For an existing custom Kindo app, open it and edit its SAML settings. Skip the creation steps and continue with the SAML configuration below.

To create an application:

  1. In the Okta Admin Console, open Applications and Resources → Applications.

  2. Select Create App Integration.

  3. Select SAML 2.0, then Next.

  4. Enter an application name. Select Next to open Configure SAML.

Configure SAML for the application:

  1. Enter these settings:

    Okta fieldValue
    Single sign-on URLKindo ACS URL
    Audience URI (SP Entity ID)Kindo SP Entity ID
    RecipientKindo ACS URL
    DestinationKindo ACS URL
    Default RelayStateLeave blank
    Name ID formatEmailAddress
    Application usernameEmail

    The email address must match the user’s Kindo email address on your organization’s verified domain.

  2. Under Attribute Statements, add attributes with these exact names.

    NameValue
    emailuser.email
    givenNameuser.firstName
    surnameuser.lastName

    The email attribute and Name ID must contain the same address. The recommended givenName and surname attributes populate the user’s display name.

  3. Select Next.

  4. Select I’m an Okta customer adding an internal app.

  5. Select Finish.

For field details, see the Okta SAML application reference.

These steps are the same for the catalog app and a custom app. Use metadata XML to import the IdP settings:

  1. On the application’s Sign On tab in Okta, open the Metadata URL and save the page as an .xml file.

  2. In Kindo, open Settings → SSO → Identity Provider (IdP) Configuration.

  3. Select Upload metadata XML and choose the downloaded file. The file imports immediately. To use pasted XML, paste the XML contents and select Import.

  4. Confirm that the certificate shows Valid until <date>.

For manual configuration:

  1. Enter these values in Identity Provider (IdP) Configuration:

    Kindo fieldOkta value
    IdP Entity IDIssuer
    Redirect URLSign on URL
    Signing certificateFull PEM contents of okta.cert, downloaded with Download on the Signing Certificate row

    On the catalog app, these values are under More details in the SAML 2.0 section of the Sign On tab.

  2. Select Save. Confirm that the certificate shows Valid until <date>.

Users must be assigned to the Okta application to sign in.

  1. In Okta, open Assignments and assign a pilot user or group.

  2. Open Kindo in a private browser window. Select Continue with SAML SSO and enter the pilot user’s email address. Complete sign-in with Okta.

  3. Test sign-in from the Kindo tile in Okta.

  4. Assign the remaining users or groups after the pilot succeeds.

  5. If your organization requires SSO, enable SSO Enforcement. Test a fresh sign-in with enforcement enabled.