Okta and Other OIDC Providers

Connect Okta, or any identity provider that supports OpenID Connect, as your SSO provider.

Use Okta or other OIDC for Okta and for any identity provider that supports OpenID Connect (for example OneLogin, JumpCloud, Ping Identity or Auth0).

Create the app in Okta

  1. In the Okta Admin Console, go to Applications → Applications and click Create App Integration.
  2. Sign-in method: OIDC - OpenID Connect. Application type: Web Application. Click Next.
  3. App integration name: for example ArmorIQ.
  4. Grant type: keep Authorization Code.
  5. Sign-in redirect URIs: replace the example with the Redirect URI shown on the ArmorIQ setup page:
https://sso.armoriq.ai/callback
  1. Sign-out redirect URIs: remove the example; ArmorIQ does not need one.
  2. Assignments: choose who may use ArmorIQ, either everyone in your organization or specific groups.
  3. Click Save. On the app's General tab, copy the Client ID and Client secret.

Find your issuer URL

The issuer URL identifies your Okta authorization server:

Okta setupIssuer URL
Most organizationshttps://<your-okta-domain>, for example https://acme.okta.com
A custom authorization serverhttps://<your-okta-domain>/oauth2/<server-id>, for example https://acme.okta.com/oauth2/default

For other providers, the issuer is the issuer value in the provider's OpenID configuration at <issuer>/.well-known/openid-configuration.

Connect it in ArmorIQ

  1. In Settings → Single sign-on, under Identity provider, choose Okta or other OIDC.
  2. Issuer URL: paste the issuer, starting with https://.
  3. Client ID and Client secret: paste the values from Okta.
  4. Name on the sign-in page (optional): for example Acme Okta.
  5. Click Save connection.

ArmorIQ checks the issuer when you save. It must be reachable over the public internet and publish an OpenID configuration that names the same issuer.

Your identity provider must mark users' email addresses as verified (the email_verified claim). Okta does this for activated users. A user whose email is not verified cannot sign in with SSO.

Next: test the connection and turn SSO on.

On this page