Okta

This guide will teach you how to set up the connector between Okta and Clarity Security.

Estimated time to complete: 5 minutes

Below are capabilities supported by the connector at this time.

Before You Begin

To successfully connect Okta and Clarity Security,  you'll need the following pre-requisites before you begin:

1.  Admin access within your Okta portal.
   •  Note: If you do not have admin access, contact your Okta admin for provisioning.
2. Admin access within your Clarity Security tenant
   •  Note: If you are a full admin in Clarity Security and get a permission error when trying to add a new application, reach out to support@claritysecurity.io.

How to Setup the Connector

Step 1: Log in to Okta Admin Portal

https://tenant-name.com/app/login 

Each Okta tenant will have its own unique admin URL.  Contact your Okta admin for your specific URL

Step 2: Head to Security > API

From the landing page after login

Step 3: Click Create Token

Click the "Create Token" button to generate a new token.

Step 4: Name your Token

Give your token a descriptive name, such as Clarity Security Connector, then click "Create Token" to finalize the token creation.

Step 5: Copy your Token value

Copy the Token value into a secure and retrievable location; this will be needed in a later step.  Okta will not provide this token again, and you need to create a new token if the original value is not saved or lost.

Step 6: Log in to Clarity

Login to your Clarity Security tenant with admin access.

Step 7: Click on Applications > Marketplace

Navigate to the applications section and then click "Marketplace".

Step 8: Click Connect

Click Connect on the Okta option from the marketplace to begin configuring your application connector.

Step 9: Connect App

Complete the App Settings form.  Details for fields common to all applications can be found in the following article: Common App Configuration Steps.

• api_token: This value is from was generated and saved during Step 5
• okta_domain: This value was from the Login process in Step 1.  
  • It should look like this: "dev-1234567". "dev-1234567" comes from the beginning of the tenant url used for login.
    •  (https://dev-1234567.okta.com from the above example)

Step 10: App Settings

Complete the App Settings form.  Details for each field can be found in the following article: Common App Configuration Steps.

Step 11: User Settings

Complete the User Settings form, check the table at the top to see if any features are unsupported.  Details for each field can be found in the following article: Common App Configuration Steps.

Step 12: Validate Your Selections and Save

Need Help?