Okta Integration Guide

Through the Okta integration, testRigor users have the ability to use an Identity Provider to power Single Sign On (SSO). This article details how to configure Okta as the Identity Provider to enable SSO with the testRigor application.

Supported Features

  • Single Sign-On (OpenID Connect) initiated via Okta.
  • Automatically creates user accounts in testRigor when Single-Sign-On is initiated by your Okta users.


In order to proceed with configuring login with SSO through Okta, you must:

  1. Have access to an Okta tenant.
  2. Be an Okta administrator to that tenant.
  3. Have a testRigor account, if you still don't have one you can get yours now.
  4. Be an administrator in testRigor and owner of a project.
  5. Complete the steps below to set everything up.

Configuration Steps

The following documents the configurations for setting up the OIDC integration between testRigor and Okta. Okta is the Identity Provider (IDP) and depending on the use case, the user will be redirected to Okta for authentication if no session has been established. To configure your provisioning settings for testRigor in Okta, there are two main steps to follow:

Step One - Add the testRigor App to Okta

  1. Login to your organization’s Okta tenant and select the Classic UI.
  2. Navigate to Applications > Applications > Add Application, search for testRigor, and then click Add.
  3. Enter an Application Label in General Settings. This is the name under which the testRigor app will appear in your Okta dashboard.
  4. Click Done.
  5. Then under the General tab of the testRigor application, copy the Client ID, the Client Secret and the Okta Domain (or Issuer URL), which is the URL you are accessing your Okta tenant (https://example.okta.com). You will need this values to enter in the testRigor configuration form.
    Note: These values allow testRigor to communicate with Okta. The Client ID is a public identifier for the client that is required for all OAuth/OIDC flows. The Client Secret is a private identifier which you should not share or broadly distribute.
  6. Before leaving Okta, ensure you have given yourself and any other target users access to the testRigor application. You can do this by going to Applications > testRigor > Assignments tab and then assigning to either the target people or group.

Step Two - Configure Okta credentials in testRigor

  1. Login to your testRigor account and navigate to the profile's page.
  2. Click the "Add Okta Credentials" button in the profile's page. If this button is not displayed, please contact us through our support channels on Slack or through our support page.
  3. In the form which will appear, enter the Client ID, Client Secret and Domain/Issuer.
  4. Click save.
  5. If the values provided in step 2.3, above, are correct, you will see a success message telling you that the Okta credentials was saved successfully.
  6. Now, in the profile's page you will see the Okta credentials configured to your company. You need to copy and share with your collaborators the Login URL. They will only be able to login using their okta account through this link, otherwise the login button for Okta will not appear in the login page.

Assign People or Groups

To give people or groups access to the testRigor application, click the Assignments tab under the configured testRigor app, then click Assign. Leveraging Groups is recommended to assign access. If assigning access to People, ensure the User Name is a valid email.
Users assigned directly or via group will now be able to log into testRigor via SSO through the testRigor app on their Okta dashboards. Keep in mind, accounts won't be created in testRigor until the initial SSO login.


TestRigor's integration with Okta leverages Okta only for authentication. To assign permissions for testRigor, users must do so directly within testRigor.