Connect Okta with OIDC

Available onEnterprise

Who can do thisWorkspace owners in Infyva, and an Okta super admin or app admin

This guide adds Infyva to Okta as an OpenID Connect web application. For SAML, use Connect Okta with SAML.

Before you start

• Your workspace is on Enterprise. Single sign-on is not part of Starter, Pro or the Pro trial.
• You are a workspace owner in Infyva. Admins can open the page and choose the role new teammates get, but only owners can connect a provider, verify domains or turn SSO on.
• You can add a DNS TXT record for your company email domain, or you know who can.
• You can open Infyva's SSO page: in the sidebar click Settings, then Single sign-on (under Security). If the page shows Set up single sign-on with Coming soon, single sign-on is not switched on for your workspace yet. Email support@infyva.ai.
• Keep a second browser window, or a private window, for testing. Stay signed in to Infyva as an owner in the first one until SSO works.

Values to copy from Infyva

Open Settings > Single sign-on in Infyva and choose the OIDC tab. Copy the Redirect URL.

In Infyva	Paste into	Value
Redirect URL	Sign-in redirect URIs	https://sso.infyva.ai/api/oauth/oidc

Step 1: Create the app integration

1. Sign in to the Okta Admin Console.
2. Go to Applications > Applications and click Create App Integration.
3. Choose OIDC - OpenID Connect, then Web Application, and click Next.
4. Set App integration name to Infyva.
5. Under Grant type, keep Authorization Code.
6. Under Sign-in redirect URIs, remove the example and paste Infyva's Redirect URL.
7. Remove the example under Sign-out redirect URIs. Infyva does not use it.
8. Under Assignments, choose Limit access to selected groups and pick the groups that use Infyva, or choose Skip group assignment for now and assign people in Step 3.
9. Click Save.

Okta's guide: Create OIDC app integrations.

Step 2: Copy the client details

On the app's General tab, under Client Credentials:

1. Copy the Client ID.
2. Copy the Client secret with its copy button.

Your Discovery URL is your Okta domain followed by /.well-known/openid-configuration, for example https://northwind.okta.com/.well-known/openid-configuration. If your team uses a custom authorization server, use its discovery URL instead, for example https://northwind.okta.com/oauth2/default/.well-known/openid-configuration.

Step 3: Assign people

1. Open the Assignments tab.
2. Click Assign > Assign to People or Assign to Groups. Assign yourself.

Claims Infyva reads

Infyva asks for the openid, email and profile scopes. Okta returns these claims for them by default.

Claim	Used by Infyva for
email	Email (required). Its domain must be verified in Infyva.
given_name	First name
family_name	Last name

Groups and roles are ignored.

Step 4: Save the connection in Infyva

1. In Infyva, on the OIDC tab, fill in Discovery URL, Client ID and Client secret.
2. Click Save connection.

You see Identity provider connected.

Verify your email domain in Infyva

Only people whose email address is on a verified domain can sign in with SSO.

1. In Infyva, on the Single sign-on page, go to 2 Verify your email domain.
2. Type your domain, for example northwindlabs.com, and click Add domain.
3. Copy the Name and Value with their Copy buttons and add them as a TXT record at your DNS provider.
4. Click Check now. When the badge changes from Waiting for DNS to Verified, you are done.

DNS changes can take a few minutes, sometimes longer. Details and limits: Verify your domain.

Turn on SSO and test it

Infyva has no separate test button. You test by signing in.

1. Go to 3 Turn it on. Switch on Allow sign-in with SSO.
2. Under New teammates join as, choose Recruiter or Viewer. This is the role a person gets the first time they sign in with SSO.
3. Click Save.
4. In a private window, open the Infyva sign-in page.
5. Type your work email in the email field, then click Sign in with SSO. Do not type a password.
6. Sign in at your identity provider. You come back to Infyva and land in your workspace.

The Status panel on the right now shows On and the time of the Last SSO sign-in. The sign-in is also in your audit log.

Start sign-in from Infyva

Infyva supports sign-in that starts on the Infyva sign-in page. Sign-in that starts from a tile in your provider's app launcher, or from a provider's own Test button that signs in from the provider side, is not supported. Point the tile at https://www.infyva.ai/auth/login, or hide it.

Require SSO

Once one SSO sign-in has worked, you can make SSO the only way in for your verified domains.

1. On the Single sign-on page, switch on Require SSO. The switch stays greyed out until the first successful SSO sign-in.
2. Click Save.

From then on:

• People on your verified domains can no longer sign in with a password. They see Your workspace requires single sign-on. Use "Sign in with SSO" instead.
• Password sessions that were already open for those people end. Someone already signed in is asked to sign in again when their current session runs out.
• Workspace owners keep password sign-in, so an owner can still get in if your identity provider is down. Read Require SSO and the owner fallback before you turn this on.

To also protect links you send to hiring managers, see Require SSO on hiring-manager links.

Roll back

• To pause SSO, switch off Allow sign-in with SSO and click Save. Everyone signs in with passwords again.
• To remove it completely, click Turn off and remove SSO in the Status panel. People keep their Infyva accounts.
• If you click Replace and save a new connection, Infyva turns Require SSO off until someone signs in with SSO again. This stops a broken connection from locking your team out.

Troubleshooting Okta (OIDC)

What you see	Likely cause	Fix
Okta: The 'redirect_uri' parameter must be a Login redirect URI in the client app settings	The Sign-in redirect URIs entry is not exactly Infyva's Redirect URL	Paste the Redirect URL again with the Copy button
Okta: User is not assigned to the client application.	The person is not assigned	Assign them on the Assignments tab
Infyva: The discovery URL didn't return an OpenID configuration.	The URL is missing /.well-known/openid-configuration	Use the full discovery URL from Step 2
Infyva: <email> is not on a verified domain for this workspace.	The person's Okta email is on a domain you have not verified	Verify the domain, or correct their email in Okta

More: Troubleshooting SSO and Okta's developer guide for OIDC apps.

Limits in this release

• No SCIM. Infyva does not receive user or group updates from your provider. Accounts are created the first time someone signs in. When someone leaves, block them in your provider and choose Suspend account in Settings > Team and roles. Remove alone is not enough: a removed person who can still sign in at your provider joins again on their next SSO sign-in.
• No group or role mapping. Everyone who joins through SSO gets the role set in New teammates join as. Change roles afterwards in Team and roles.
• Sign-in starts from Infyva. Sign-in started from your provider's app tile is not supported.
• One identity provider per workspace. Saving a new one replaces the old one.
• Metadata is read once. If you give a metadata URL, Infyva reads it when you click Save connection. After a certificate change at your provider, save the connection again.
• Team members only. Candidates never sign in with SSO.

Next steps

• Require SSO and the owner fallback
• Accounts, roles and limits