- What is TestInvite?
- Build Your First Test
- Run Your First Assessment
- Taking the Assessment
- Viewing the Results
- Question Bank Overview
- Common Question Features
- Scoring
- Question Types
- Question Authoring
- Browsing Questions
- Content Blocks
- Media Library
- Metadata Rules & Schema
- Tests Overview
- My Tests
- Creating a Test
- The Test Editor
- Test Settings
- Sections & Pages
- Adding Questions
- Page Builders
- Test Profile
- Reporting
- Test Papers
- Analytics
- Publishing a Test
- Test Library
- Marketplace
- Tasks Overview
- Creating a Task
- Task Dashboard
- Steps
- Task Settings
- Candidates
- Test Sessions
- Sent Mails
- Proctoring
- Analytics
- Analytics Overview
- Test Analytics
- Question Analytics
- Per-Question Analytics
- Results Explorer
- Segment Analysis
Set Up SSO with Okta
In Okta, TestInvite is an app integration (SAML 2.0 or OIDC web application); for SAML, Okta's metadata URL fills in TestInvite in one step, and people must be assigned to the app.
This guide is for the Okta administrator. Replace <ORG-ID> with your TestInvite organization ID and company.okta.com with your Okta domain.
Option A — SAML 2.0
- Okta Admin Console → Applications → Applications → Create App Integration → SAML 2.0 → Next.
- App name
TestInvite→ Next. - Single sign-on URL:
https://www.testinvite.com/api/v1/auth/sso/<ORG-ID>/saml/acs, keep Use this for Recipient URL and Destination URL checked. - Audience URI (SP Entity ID):
https://www.testinvite.com/api/v1/auth/sso/<ORG-ID>/saml/metadata. - Name ID format: EmailAddress; Application username: Email.
- Attribute Statements:
email→user.email,firstName→user.firstName,lastName→user.lastName(name format Unspecified). - Next → I'm an Okta customer adding an internal app → Finish.
- On the Sign On tab, copy the Metadata URL.
- On the Assignments tab, assign the people or groups who may sign in.
In TestInvite, protocol SAML 2.0, paste the Okta metadata URL into Identity provider metadata URL → Import. Add your email domains and run Test SSO.
Okta dashboard tile: in the app's General tab, set Initiate login URI to https://www.testinvite.com/api/v1/auth/sso/<ORG-ID>/initiate (and choose to send users there), so the tile starts sign-in at TestInvite. Otherwise turn on Allow sign-in from the identity provider portal in TestInvite.
Option B — OpenID Connect
- Create App Integration → OIDC - OpenID Connect → Web Application → Next.
- App name
TestInvite; grant type Authorization Code; Sign-in redirect URIs:https://www.testinvite.com/api/v1/auth/sso/<ORG-ID>/oidc/callback; remove the sign-out redirect URI; choose who gets access → Save. - Copy the Client ID and the Client secret from the General tab.
- Issuer URL:
https://company.okta.com(the org authorization server). If you use a custom authorization server, use its issuer, e.g.https://company.okta.com/oauth2/default. - Client authentication: Basic (Okta's default, Client secret basic)
- Scopes:
openid email profile