SSO With Okta
Last modified on August 10, 2022
This document details the steps to set up Okta single sign-on (SSO) to manage authentication for strongDM.
- OpenID Connect (OIDC) must be enabled for your account. If it is not, please contact Okta Support and request that they enable it. This can be completed in minutes.
- You must be a strongDM user with the Administrator Permission Level and a User with administrator rights in your Okta account.
- Currently, strongDM only supports Service Provider Initiated (SP-Initiated) SSO.
These steps describe how to create an OIDC app using Okta’s App Integration Wizard (AIW).
- Log in to Okta.
- From the Admin Console, go to Applications > Applications and click Browse App Catalog (if you have already added the strongDM app through our User & Group Provisioning guide you can skip to Step 7).
- Search for and select the “strongDM” app, then click Add.
- Change the label for the app if you’d like, then click Done.
- On the Sign On tab, click Edit in the upper-right, then in the Credentials Details section set Application username format to “Email”.
- Click Save.
- From the Client Credentials section, copy the Client ID and Client secret values. You will need these values in the next step.
- Lastly, copy the app’s Okta domain (
https://<YOUR-ORG>.okta.com), which will be the single sign-on URL in the next step.
- Enter the account details in the strongDM Admin UI. Go to Settings > User Management. In the Single Sign-on section, click the lock icon to set the following:
- Provider: Select Okta.
- Single sign-on URL: Add your Okta domain (
- Client ID: Paste your client ID.
- Client Secret: Paste your client secret.
- Select your desired general SSO settings and click activate.
- Go back to Okta and confirm Okta access. Confirm that the email addresses for all users are identical in both strongDM and in Okta. Confirm that all users who you intend to grant database access have access to the strongDM application by default, and if all of the above is true, you should be ready to enable SSO.
If any errors occur or if the integration fails in any way, please contact firstname.lastname@example.org for assistance.