Skip to content
  • There are no suggestions because the search field is empty.

Okta (OIDC)

How to set up Okta Single Sign-on in TestMonitor.

Single Sign-on (SSO) is an authentication method that lets users log in using Okta as the trusted third party. This allows users to use one set of credentials for multiple programs. SSO can also be used to auto provision new accounts for your employees instead of manually creating or inviting them as users.

Please note that you must have a Professional or Enterprise plan subscription to access this feature.

Before You Begin

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

  • Have access to an Okta tenant.
  • Be an Okta administrator to that tenant.

  • Make sure that the TestMonitor user' emails exactly match their Okta accounts.

Complete the steps below to set everything up.

Install TestMonitor app in Okta

Before you can configure SSO in TestMonitor, you'll need to install the TestMonitor application in your Okta instance:

  1. In your Okta Admin Console, go to Applications > Applications.
  2. Click Browse App Catalog and search for "TestMonitor".
  3. Click the application tile and click Add Integration.
  4. Follow the on-screen instructions to complete the installation.
  5. Once installed, open the TestMonitor application in your applications list.
  6. Take note of the Client ID and Client Secret values - you'll need them at a later stage.

That's it - you're now ready to configure SSO in TestMonitor.

Configure Single Sign-on in TestMonitor

Once the TestMonitor app has been installed in your Okta instance, you can proceed with configuring TestMonitor:

  1. Click on the gear icon on the top to head over to the general settings.
  2. Under Security in the left menu, select Single Sign-on.
  3. Toggle the switch to Use Single Sign-on.
  4. Select Okta as your SSO provider.
  5. Provide the URL of your Okta authorization server (for example, https://myserver.okta.com).
  6. Enter the Client ID and Client Secret you've noted down earlier while installing the TestMonitor app in your Okta instance.
  7. Click Save to finish your configuration and enable Single Sign-on.

When Single Sign-on is enabled, you can continue with configuring auto-provisioning.

Configure Auto Provisioning

Auto provisioning means that if a user without an existing TestMonitor account attempts to sign in, an account will automatically be created for them. If Auto Provisioning is switched off, only users that already have an account in TestMonitor can sign in. If you select to turn auto provisioning on, then you will have additional information you can fill in:

  • Allowed domains: Only users with email addresses that match one of these domains will be provisioned.
  • Project for new users: This is an optional section to specify which project new users will automatically be provisioned to.
  • Role for new users: This is an optional section to specify what role new users will automatically be provisioned to.

Sign in with Okta

If SSO is configured, you will see Sign in with Okta as an option on your TestMonitor login page.

Click this button and, if you haven’t already, fill in the email address and password of your Okta account to log in. You are now also automatically logged in to TestMonitor.

Disable Single Sign-on

To disable SSO:

  • Click on the gear icon on the top right for Settings.
  • Under Access & Security in the left menu, select Single Sign-on.
  • Toggle the switch off for Use Single Sign-on.

Troubleshooting

Users cannot sign in and see “access denied” or “not assigned” errors

This usually occurs when users have not been assigned to the application in Okta.

  • Ensure the user is assigned to your app under Applications → TestMonitor → Assignments.
  • Verify any group-based assignments are correct, especially if using automated group provisioning.

A user cannot sign in but others can

This often results from missing assignments, role misconfigurations, or unapproved applications.

  • Check that all affected users are properly assigned to the app.
  • Confirm that Okta user attributes (email, username, etc.) match what your app expects.
  • Review Okta app settings for any restrictions, such as network zones or access policies.

The consent screen or login page appears repeatedly

This can happen if the app requires admin approval or if session tokens expire.

  • If your app requires admin consent for certain permissions, ensure an Okta admin has approved access.
  • Users may need to log out and back in to refresh session tokens.