Okta SAML Setup June 6, 2025 8 min read

Setting up Okta with Thinkific via WooNinja SSO

A step-by-step guide to configuring Okta as your SAML identity provider for Thinkific.

Okta is one of the most common identity providers for mid-market and enterprise companies. This guide walks through connecting Okta to Thinkific using WooNinja SSO as the SAML service provider.

What you will need

  • Okta admin access to create an application integration.
  • Your Thinkific admin panel and WooNinja SSO configuration screen.
  • Agreement on the unique identifier (NameID) and attributes to release, usually email and first/last name.

Step 1: Create the Okta app integration

  1. In Okta, go to Applications > Applications and click Create App Integration.
  2. Choose SAML 2.0 and click Next.
  3. Give the app a name such as "Thinkific SSO" and upload a logo if desired.
  4. Click Next to configure SAML.

Step 2: Configure SAML settings

Use the values provided in your WooNinja SSO settings page:

  • Single sign-on URL — the WooNinja SSO assertion consumer service URL.
  • Audience URI (SP Entity ID) — the WooNinja SSO entity ID.
  • Name ID format — usually EmailAddress or Persistent.
  • Application username — typically Email.

Step 3: Add attribute statements

Add at least the following attribute statements:

| Name | Value | |-----------|----------------| | email | user.email | | firstName | user.firstName | | lastName | user.lastName |

If you want to map Okta groups to Thinkific bundles or collections, add a groups attribute that returns the relevant group names.

Step 4: Complete Okta setup and copy metadata

Finish the Okta wizard and copy the Metadata URL from the Sign On tab. Paste this URL into WooNinja SSO and save the connection.

Step 5: Test the login

Assign a test user in Okta, open an incognito window, and visit your Thinkific sign-in page. Click Sign in with SSO and log in as the test user. If the user is created or matched correctly, the connection is working.

Common pitfalls

  • Audience mismatch — double-check the SP entity ID.
  • NameID not released — confirm the NameID format matches on both sides.
  • Missing attributes — use the WooNinja SSO logs to inspect the assertion and verify attributes.

For help with advanced Okta configurations such as group-based enrolment or Just-In-Time provisioning, contact WooNinja support.

Written by WooNinja Team
Back to blog

Related articles