Single Sign-On
Connect your identity provider over SAML 2.0 or OpenID Connect so employees sign in to TechClass with their corporate credentials.
Single Sign-On (SSO) lets your employees sign in to TechClass with the identity provider (IdP) they already use, such as Microsoft Entra ID, Okta or Google Workspace, over SAML 2.0 or OpenID Connect (OIDC).
To open it, go to Configuration > Single Sign-On in the Admin Portal sidebar. The page has two tabs: Connections and SP Metadata.
Add-on required
Single Sign-On needs the Security+ add-on. Without it the page shows what the add-on includes and a Talk to sales button. See Billing.
1. How It Works
When a connection is enabled, the login page shows a button for it, named after the connection's display name. A user who clicks it is sent to your IdP to authenticate and comes back signed in. With Just-in-Time provisioning, a person who does not have an account yet gets one on their first SSO sign-in, from the name and email your IdP provides. Signing out of TechClass ends the TechClass session only, not your IdP session.
| Protocol | Typical providers |
|---|---|
| SAML 2.0 | Microsoft Entra ID, Okta, ADFS, PingFederate, OneLogin |
| OpenID Connect | Okta, Google Workspace, Auth0, Microsoft Entra ID (v2) |
2. Connections
Click Add Connection and choose the protocol.
Common settings
- Display Name: The label on the login page button, for example "Sign in with Acme Corp".
- Enabled: Show the connection on the login page.
- Enforce SSO: Hide the password form so everyone must sign in through the IdP. Keep a working admin session before enabling it.
- Allow Just-in-Time Provisioning: Create accounts automatically on first SSO sign-in.
- Claim Mapping: Which claims carry the user's email, first name and last name, if your IdP uses non-standard names.
OpenID Connect
Enter the Authority / Issuer URL, the Client ID and Client Secret from the application you registered at your IdP, and the Scopes (the default openid profile email is right for most providers).
SAML 2.0
Enter the IdP Entity ID, the IdP SSO URL and the IdP Signing Certificate in PEM or Base64 form, all from your IdP's SAML application.
Click Save Connection. Edit or disable a connection from its row at any time.
3. SP Metadata
Your IdP needs to know about TechClass as a service provider. The SP Metadata tab gives you the values to enter, or a metadata file to upload.
- Assertion Consumer Service (ACS) URL: Where your IdP posts the SAML assertion after authentication.
- SP Entity ID: The identifier of TechClass as a service provider.
- SP Metadata XML: The same information as a file. Download metadata.xml or Copy it, and import it into your IdP.
4. Security Guardrails
- Replay protection: Each SAML assertion is accepted once.
- Clock skew: Up to 3 minutes of drift between your IdP and TechClass is tolerated.
- Domain uniqueness: An email domain routes to one connection only, and public mail domains such as gmail.com cannot be used for SSO routing.