All Collections
Okta configuration guide
Okta configuration guide

How to set up Okta Single Sign-On integration

Updated over a week ago


  • Supported features

  • Requirements

  • Configuration steps

  • SP login flow initiation

  • Notes

Supported features

  • Single Sign-On (OpenID Connect) initiated via Taktile

  • Automatically creates user accounts in Taktile when Single-Sign-On initiated by your Okta users


  1. Install the Taktile application in your Okta instance

  2. If you haven't already, sign up and create a Taktile Workspace

  3. Make sure that the Workspace members' emails exactly match their Okta accounts

  4. Complete the steps below to set everything up

​Configuration steps

After installing the application, you need to obtain some information that you will have to send to Taktile. You will also need to edit one of the App-settings.

Gather information from Okta

  1. In the Okta admin page, click on the Taktile application and then navigate to the Sign On tab.

  2. Copy the values of the Client ID and Client secret (click the eye button to toggle the visibility).

  3. There should be a section that has a link titled OpenID Provider Metadata. Click on this link. In the JSON document shown, look for a key titled “issuer” and copy the URL-value

Send the information to Taktile

Once you have all the information (summarized below), mail it to [email protected]

  • Client ID

  • Client Secret

  • Issuer URL

Taktile support will handle your request and get back to you once the integration is configured.

Edit Taktile app

Editing from within the app is on our roadmap; if your credentials change before the feature is shipped, please contact support.

SP login flow initiation

1. Go to the Taktile
2. Click Sign in with Okta


To best utilize the Okta integration for your organization, create a Taktile Flow with some general instructions that will greet new users. To do this:

  1. create a Workspace visible Team

  2. Create a Team visible Board

  3. This Board is now accessible to all Workspace members (read-only).

Did this answer your question?