Single sign-on
A workspace admin can connect the client’s own identity provider, so their staff sign in to Identiguard the same way they sign in to everything else. Okta and Microsoft Entra ID are supported, using OpenID Connect.
Open Single sign-on under Workspace. Only admins see it in the sidebar. Single sign-on is available on every plan.
For the task from start to finish, see Set up single sign-on.
| Rule | Detail |
|---|---|
| Connections for each workspace | One |
| Email domains for each connection | One |
| The same domain in two workspaces | Not possible. A domain can be verified by one workspace only. |
| Public email domains, such as gmail.com and outlook.com | Refused |
| When it starts to work | Only after the domain is verified with a DNS record |
1. Create an application in the identity provider
Section titled “1. Create an application in the identity provider”On the Single sign-on page, choose Okta or Microsoft Entra ID. The page then shows numbered setup steps for that provider and the Callback / redirect URI (configure in your IdP). Use the copy button beside it. You see Callback URL copied.
- In the Okta Admin Console, go to Applications → Create App Integration → OIDC → Web Application.
- Set the Sign-in redirect URI to the callback URL.
- Under Assignments, give access to the users or groups who should reach Identiguard.
- Copy the client ID and client secret.
The issuer is the Okta org URL, for example https://your-org.okta.com, or a custom authorisation server URL.
Microsoft Entra ID
Section titled “Microsoft Entra ID”- In the Entra admin centre, go to App registrations → New registration.
- Set the Redirect URI (Web) to the callback URL.
- Under Certificates & secrets, create a client secret.
- Copy the application (client) ID and the secret value.
The issuer is https://login.microsoftonline.com/<your-tenant-id>/v2.0.
2. Create the connection in Identiguard
Section titled “2. Create the connection in Identiguard”| Field | What to enter |
|---|---|
| Issuer URL | The issuer for the provider, as described above |
| Client ID | The client ID from the application |
| Client secret | The client secret from the application |
| Email domain | The bare domain, such as client.com. No https:// and no path. |
The helper text under Email domain reads: “People signing in with this email domain are routed to your IdP (after DNS verification).”
Choose Create connection. You see SSO connection created. Now verify your domain.
3. Verify the domain
Section titled “3. Verify the domain”The page now shows the panel Verify domain ownership.
- Copy Name. It is
_idnguard-verify.followed by your domain, for example_idnguard-verify.client.com. - Copy Value. It is a token that Identiguard generated for this connection.
- At the DNS host for the domain, create a TXT record with that name and that value.
- Choose Verify domain.
| Badge | Meaning |
|---|---|
| Awaiting domain verification | The connection exists but is not used for sign-in yet |
| Live | The record was found. Single sign-on is working. |
When it works you see Domain verified. SSO is live. If the record is not visible yet, the panel shows a TXT record not found message. DNS changes can take a few minutes. Wait and choose Verify domain again.
What happens once it is live
Section titled “What happens once it is live”- Anyone who signs in with an email address at that domain is sent to the identity provider.
- They join the workspace automatically the first time they sign in.
- Passkey sign-in is refused for accounts at that domain. Those people see “Passkey sign-in is disabled for this account. Use your organisation’s single sign-on.”
- An invitation link for an address at that domain shows Continue with single sign-on in place of the email setup button.
The role new people get
Section titled “The role new people get”A person who joins through single sign-on is a member by default. If a pending invitation exists for their address, they get the role on the invitation. For a person who is already a member, the higher of the two roles is kept.
Change a role afterwards on the Members page. See Members and roles.
Restrict membership to SSO
Section titled “Restrict membership to SSO”Restrict membership to SSO appears once the connection is Live. It is a button that reads Off or On. Choose it to change the state.
| State | Effect | Message |
|---|---|---|
| On | Email invitations are blocked. New members can join only through the identity provider. | Membership is now restricted to SSO. Email invitations are blocked. |
| Off | Email invitations work next to single sign-on. | Email invitations re-enabled alongside SSO. |
Turn it off for a short time to invite a guest from outside the domain, then turn it on again. The steps are in Set up single sign-on.
Remove it
Section titled “Remove it”- Choose Remove connection.
- The browser asks: “Remove this SSO connection? Users keep their accounts and memberships.” Confirm.
You see SSO connection removed.
People keep their accounts and their workspace memberships. People at that domain then need a passkey to sign in. Each of them requests a setup link from Create account / set up a passkey on the sign-in page.
Troubleshooting
Section titled “Troubleshooting”Creating the connection
Section titled “Creating the connection”| What you see | Why | What to do |
|---|---|---|
| Bad Request: issuer does not look like a valid Okta issuer or …Microsoft Entra ID issuer, with an example | The Issuer URL is wrong for the chosen provider. | Okta: use the org URL or a custom authorisation server URL. Entra ID: use https://login.microsoftonline.com/<tenant-id>/v2.0. |
| Bad Request: clientId and clientSecret are required. | Client ID or Client secret is empty. | Fill in both. |
| Bad Request: Enter a bare domain like client.com (no scheme or path). | Email domain has https:// or a path. |
Enter the domain alone. |
| Bad Request: Public email provider domains cannot be used for SSO routing. | The domain is a public email provider. | Use the organisation’s own domain. |
| This workspace already has an SSO connection. Remove it first. | A workspace can have one connection. | Remove the existing one, then create the new one. |
| The domain … is already verified by another connection. or …by another workspace. | Another workspace has claimed the domain. | The other workspace removes its connection, or contact support. |
| Could not read the identity provider’s OpenID configuration: with a reason | Identiguard could not reach or trust the provider’s discovery document. | Check the Issuer URL and that the identity provider is reachable. |
| Could not register the identity provider. with or without a reason | Registration failed. | Check the client ID and secret, then try again. |
| Failed to save SSO connection | The server gave no usable message. | Try again. If it continues, tell support the time and the page. |
Verifying the domain
Section titled “Verifying the domain”| What you see | Why | What to do |
|---|---|---|
TXT record not found on _idnguard-verify. and your domain, then DNS changes can take a few minutes to propagate. |
The record is missing, has the wrong name or value, or is not visible yet. | Check the record at the DNS host. Wait a few minutes. Choose Verify domain again. |
| Domain already verified. | You chose Verify domain on a live connection. | Nothing to do. |
| This connection’s identity provider no longer matches the domain that was verified. Remove the connection and set it up again. | The provider and the verified domain no longer match. | Remove the connection and create it again. |
| Verification failed | The server gave no usable message. | Try again in a few minutes. |
Other messages
Section titled “Other messages”| What you see | Why | What to do |
|---|---|---|
| Verify the domain first. SSO-only membership requires a live connection. | Restrict membership to SSO was changed before the domain was verified. | Verify the domain first. |
| No SSO connection configured for this workspace. | The connection was removed in another tab or by another admin. | Reload the page. |
| Copy failed. Select and copy manually. | The browser blocked the clipboard. | Select the text and copy it by hand. |
| Failed to load SSO status | The page could not load the connection. | Reload the page. |
| Forbidden: only workspace admins can manage single sign-on. | You are not an admin of the workspace. | Ask an admin. |
Messages people see when they sign in are in Signing in.