Connect Okta with SAML

Available onEnterprise

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

This guide adds Infyva to Okta as a SAML 2.0 app integration. It takes about 10 minutes, plus DNS time. For OpenID Connect, use Connect Okta with OIDC.

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 SAML tab under 1 Connect your identity provider. Copy these with the Copy buttons in the box Enter these in your identity provider.

In Infyva	Paste into	Value
ACS URL (reply URL)	Single sign-on URL	https://sso.infyva.ai/api/oauth/saml
Entity ID (audience)	Audience URI (SP Entity ID)	https://sso.infyva.ai
Our metadata	Service provider metadata (if your provider can import it)	https://sso.infyva.ai/.well-known/sp-metadata

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 SAML 2.0 and click Next.
4. On General Settings, set App name to Infyva. You can upload the Infyva logo.
5. Under App visibility, tick Do not display application icon to users. Infyva sign-in starts from the Infyva sign-in page, not from the Okta dashboard.
6. Click Next.

Okta's guide: Create SAML app integrations.

Step 2: Paste Infyva's values

On Configure SAML:

1. Single sign-on URL: paste Infyva's ACS URL (reply URL). Leave Use this for Recipient URL and Destination URL ticked.
2. Audience URI (SP Entity ID): paste Infyva's Entity ID (audience).
3. Default RelayState: leave empty.
4. Name ID format: choose EmailAddress.
5. Application username: choose Email.
6. Update application username on: leave Create and update.

Leave the advanced settings at Okta's defaults: signed response and assertion, RSA-SHA256, assertion encryption off. Okta's field reference: SAML app integration settings.

Step 3: Add attribute statements

Still on Configure SAML, under Attribute Statements, add these three. Leave Name format as Unspecified. The names are case-sensitive.

Name	Value	Used by Infyva for
email	user.email	Email (required)
firstName	user.firstName	First name
lastName	user.lastName	Last name

Leave Group Attribute Statements empty. Infyva does not use groups.

Click Next. On Feedback, choose I'm an Okta customer adding an internal app, then click Finish.

Step 4: Copy the metadata

1. Open the app's Sign On tab.
2. Under SAML 2.0, copy the Metadata URL. If you prefer a file, open the metadata link and save the page as an .xml file.

Step 5: Assign people

1. Open the app's Assignments tab.
2. Click Assign > Assign to People or Assign to Groups, pick who uses Infyva, and click Done. Assign yourself.

Okta's guides: Assign an app to users and Assign an app to a group.

Step 6: Save the connection in Infyva

1. In Infyva, on the SAML tab, paste the Metadata URL into Or the metadata URL, or drop the saved XML file on Upload the metadata XML file.
2. Click Save connection.

You see Identity provider connected. and the step shows Connected with SAML.

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

What you see	Likely cause	Fix
Okta says the user is not assigned to the application	The person is not on the Assignments tab	Assign them, or their group
Okta shows a 400 or 404 page after you click Sign in with SSO	The app was deactivated, or the metadata in Infyva is from another app	Check the app is Active, then save its Metadata URL in Infyva again
Infyva: Your identity provider details were not accepted	The metadata is incomplete	Use the Metadata URL from the Sign On tab, not the app's sign-in URL
Infyva: That URL didn't return SAML IdP metadata.	The URL is not the metadata link	Copy Metadata URL from Sign On > SAML 2.0
Infyva: Your identity provider did not complete the sign-in. Please try again.	Okta did not send an email address	Check the email attribute statement. The name must be exactly email.
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 the person's email in Okta
An error after opening Infyva from the Okta dashboard tile	Sign-in from the tile is not supported	Start from the Infyva sign-in page. Hide the tile (Step 1).

More: Troubleshooting SSO.

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
• Require SSO on hiring-manager links