Single Sign-On (SSO)
Let your team sign in to Wisec with your own identity provider (IdP) - Microsoft Entra ID (Azure AD), Okta, Google Workspace, Ping, OneLogin, and any OpenID Connect provider.
Available on the Pro plan. SSO is configured by an organization admin.
How it works
Wisec uses OpenID Connect (OIDC) with a domain-based, SP-initiated flow:
- A user clicks Sign in with SSO and enters their work email.
- Wisec matches the email domain to your organization and redirects to your IdP.
- After the user authenticates, the IdP redirects back to Wisec, which verifies the identity token and signs the user in.
- First-time users are provisioned automatically (JIT) - but only for email domains your organization has verified.
The session that follows is identical to a normal login (secure HttpOnly cookie, refresh, logout revocation). SSO never sees or stores your users' passwords.
Redirect URI (callback)
When you create the OIDC application in your IdP, you must allow Wisec's callback URL. Register the URL that matches the environment you use:
| Environment | Redirect URI to register in your IdP |
|---|---|
| Production | https://app.wisec.io/api/v1/auth/sso/callback |
| Sandbox / evaluation | https://dev.app.wisec.io/api/v1/auth/sso/callback |
This is a setting inside your IdP (the allow-list of URLs it may redirect to). It is not a DNS record. Most providers call it Redirect URI, Reply URL, or Callback URL.
Requested scopes: openid, email, profile.
Step 1 - Create an OIDC application in your IdP
In your identity provider, register a new Web / confidential OIDC application and collect three values:
- Issuer URL (a.k.a. authority) - e.g.
https://login.microsoftonline.com/<tenant-id>/v2.0for Entra ID. - Client ID
- Client Secret
Set the redirect URI to the value from the table above.
Step 2 - Enter the connection in Wisec
Go to Settings → Single Sign-On (admin only) and fill in:
- Issuer URL, Client ID, Client Secret (the secret is stored encrypted and never shown again).
- Default role for users created on first login (Member or Admin).
Save the connection.
Step 3 - Verify your email domain
Only verified domains can sign in via SSO (this prevents anyone from claiming a domain they don't own).
- In the SSO settings, add your domain (e.g.
your-company.com). - Wisec gives you a DNS TXT record of the form
wisec-verify=<token>. - Add that TXT record at your domain root with your DNS provider.
- Click Verify. DNS changes can take a few minutes to propagate.
You can verify several domains for the same organization.
Step 4 - Enable (and optionally enforce) SSO
- Enable SSO - users from verified domains can now sign in via your IdP.
- Enforce SSO (optional) - blocks password login for verified domains, so everyone must use the IdP. Enable this only after you have confirmed SSO works, to avoid locking yourself out.
Security
- The OIDC client secret is encrypted at rest (AES-GCM) and is write-only from the dashboard.
- Each login uses a server-side state and nonce (single-use) to prevent replay and CSRF.
- The identity token is fully verified (issuer, audience, expiry, signature).
- Just-in-time provisioning is restricted to verified domains - a user is never created on the IdP's claim alone.
- SSO logins and configuration changes are recorded in the audit log.
Roadmap
OIDC is available today. SAML support (for ADFS and legacy providers) is planned as a fast-follow. If your rollout requires SAML, let us know.