---
title: "Setting up Okta SSO in Talkspirit"
description: "Talkspirit supports Okta as a SAML single sign-on provider. An administrator connects Okta under Administration, then members sign in with their Okta credentials."
category: administration-security
section: authentication-and-sso
tags: [admin]
type: Tutorial
lastUpdated: 2026-10-14
locale: en
canonical: https://support.talkspirit.com/en/administration-security/set-up-okta-sso
---

# Setting up Okta SSO in Talkspirit


Talkspirit supports Okta as a SAML single sign-on (SSO) identity provider. An administrator enables the **SAML** provider under **Administration → Authentication**, selects **Okta**, and enters the connection details from the Okta application. Members then sign in to Talkspirit with their Okta credentials. SAML SSO is included with specific plans.

## Prerequisites

- You are an administrator.
- Your plan includes SAML SSO. When it does not, the **SAML** provider shows a **Locked** badge with a contact-sales option instead of the configuration fields.
- You can create a SAML 2.0 application in your Okta admin console.

## How do I open the SSO settings?

1. Go to **Administration → Authentication**.
2. Open the **SSO Providers** tab.
3. Turn on the **SAML** provider with its switch. The card opens with the **Values for your identity provider** block, and the configuration fields expand below it.

![SAML provider card expanded on the SSO Providers tab, showing the Identity provider selector set to Okta and the connection fields (Entity ID, SSO Endpoint URL, SLO Endpoint URL, X.509 Certificate, login button label)](/images/administration-security/set-up-okta-sso/saml-card-expanded.png)

## How do I connect Okta?

Okta asks for Talkspirit's own service-provider details first: its **Create SAML Integration** wizard needs them before it shows Okta's own values. Copy them with the copy buttons of the **Values for your identity provider** block, at the top of the expanded **SAML** card. The block appears as soon as SAML is on, before anything is saved.

| Okta field | Value to copy from the SAML card |
| --- | --- |
| **Single sign-on URL** | **Reply URL (ACS URL)** |
| **Audience URI (SP Entity ID)** | **Identifier (SP Entity ID)** |

If members start sign-in from the Okta tile, enter the card's **IdP-initiated sign-in URL** as the **Single sign-on URL** instead, as its hint explains.

Once the Okta application is created, copy its **Issuer**, its **SSO URL** and its signing certificate. Then, in the expanded **SAML** card:

1. Select **Okta** from the **Identity provider** list.
2. Enter the **Entity ID (Issuer URL)**, the **SSO Endpoint URL** and the **X.509 Certificate (PEM)** from Okta. Add the **SLO Endpoint URL** if Okta provides one.
3. Click **Save SAML configuration**.

> **Tip:** Select **Import IdP metadata** to fill the endpoints and certificate automatically from Okta's metadata document, so the certificate is never retyped by hand.

The **SAML 2.0 Service Provider Metadata** link on the card only works once you have saved the configuration with a certificate and an SSO URL. Until then, the card shows it as plain text with the hint "Available once you save this configuration with a certificate and an SSO URL."

## Is Okta SSO available on all plans?

SAML SSO, including Okta, depends on your plan. When your plan includes it, the **SAML** provider is configurable as described above. When it does not, the provider is locked and shows a contact-sales option. Check your subscription or contact Talkspirit to confirm your entitlement.

## Next steps

- [Configuring SAML Authentication](/en/administration-security/saml-authentication)
- [Configuring Google Authentication](/en/administration-security/how-to-configure-google-authentication)
- [Automated user provisioning and de-provisioning (SCIM 2.0)](/en/administration-security/automated-user-provisioning-and-de-provisioning-scim-20)
