SourceLace Docs
FAQOpen the app

Single sign-on (SSO)

Have your people sign in to SourceLace through your own identity provider (Okta, Microsoft Entra ID, Google Workspace, OneLogin, Ping, JumpCloud, ADFS or any OpenID Connect or SAML 2.0 provider), add them automatically on their first sign-in, require SSO for your domains, and sync their groups.

Single sign-on is part of the Business and Enterprise plans (see Plans and limits).

Your identity provider can also keep your people and groups up to date all the time, without anyone signing in, through SCIM provisioning.

Status: OpenID Connect single sign-on is Available: built to the standard and validated with your identity provider during onboarding. SAML 2.0 is new. Tell support@sourcelace.com when you set it up so we can help with your first sign-in.

Use OpenID Connect when your identity provider offers it (almost every modern one does). Use SAML 2.0 for providers without it, such as ADFS, or when your organization's policy is SAML.

What it does

  • Sign-in. The SourceLace sign-in page, and the page an MCP client opens, offers Continue with SSO / work email next to Google and Microsoft. The person types their work email; if its domain belongs to an organization with SSO, they are sent to that organization's identity provider, sign in as they do every day, and come back signed in to SourceLace.
  • New people are added automatically. The first time someone signs in through SSO, SourceLace adds them to your organization as a member. Admins can make them admins on the People page. The People page shows them as joined by "Single sign-on".
  • Require SSO (optional). People at your chosen domains can no longer sign in with Google or Microsoft: they are sent to SSO instead. Sessions they already had that did not come through SSO, in the SourceLace app and in MCP clients, stop working at once, so they sign in again through SSO.
  • Group sync (optional). At every SSO sign-in, SourceLace reads the person's groups from your identity provider, puts them into the matching SourceLace groups, and takes them out of groups they are no longer in. See Group sync.
  • Audit. Every sign-in (including refused SSO sign-ins, and Google or Microsoft sign-ins that were sent to SSO) and every change to the SSO settings is recorded in your audit trail: who, when, how, and which groups changed. Never secrets or tokens.

How SourceLace checks a sign-in

SourceLace uses the OpenID Connect authorization code flow with PKCE, plus state and nonce. It reads your provider's addresses from <issuer>/.well-known/openid-configuration and checks the ID token in full: its signature against your provider's published keys (only public-key algorithms such as RS256, never "none" or shared-secret ones), the issuer, the audience (your client id), the expiry and the nonce. It then takes the person's address from the email claim, requires it to be at one of the domains you chose for SSO, and, when the provider sends email_verified, requires that to be true.

With SAML, SourceLace checks the signed response just as strictly: see How SourceLace checks a SAML sign-in.

Your client secret is encrypted with your organization's own key before it is stored. It is never shown again, never logged and never returned by any API: the settings screen only says it is set. A saved secret is only ever sent to the identity provider it was saved for: changing the issuer URL or client id needs the secret to be entered again.

Before you start

  1. On the People page, make sure your email domains (for example corvanta.com) are listed under Email domains. SSO can only cover domains your organization already has.

  2. Note the redirect URL to register in your identity provider. It is shown at the top of the Single sign-on tab of Sign-in in the SourceLace app. On this server it is:

    https://sourcelace.ai/login/callback
    

    If the screen lists more than one address, register all of them.

Set up Okta

  1. Sign in to the Okta Admin Console.
  2. Go to Applications → Applications → Create App Integration.
  3. Choose OIDC - OpenID Connect, then Web Application, and click Next.
  4. Fill in:
    • App integration name: SourceLace
    • Grant type: leave Authorization Code ticked.
    • Sign-in redirect URIs: the redirect URL from Before you start. Remove the example sign-out URI, or leave it empty.
    • Assignments: choose who may use SourceLace (everyone, or selected groups).
  5. Click Save.
  6. On the app's General tab, copy the Client ID and the Client secret (under Client Credentials; client authentication "Client secret"). You may tick Require PKCE as additional verification: SourceLace always uses PKCE.
  7. Issuer URL. Your Okta domain, such as https://corvanta.okta.com (shown at the top right of the Admin Console, or under Security → API). If you use a custom authorization server instead, the issuer is its address, such as https://corvanta.okta.com/oauth2/default.
  8. Email. Nothing to do: Okta sends email and email_verified with the email scope SourceLace asks for.
  9. Groups (only for group sync).
    • With the Okta domain as issuer: open the app's Sign On tab → OpenID Connect ID Token → Edit. Set Groups claim type to Filter, the claim name to groups, and the filter to Matches regex .* (or, to send only some groups, Starts with SourceLace-). Click Save. SourceLace asks for the groups scope itself when group sync is on.
    • With a custom authorization server: Security → API → Authorization Servers → your server → Claims → Add Claim: name groups, include in ID Token (Always), value type Groups, filter Matches regex .*.
    • Okta sends group names. In SourceLace, set each group's external id to the Okta group's name exactly as it appears in Okta (case does not matter).

Set up Microsoft Entra ID

  1. Sign in to the Microsoft Entra admin center (entra.microsoft.com).
  2. Go to Identity → Applications → App registrations → New registration.
  3. Fill in:
    • Name: SourceLace SSO
    • Supported account types: Accounts in this organizational directory only (single tenant).
    • Redirect URI: platform Web, and the redirect URL from Before you start.
  4. Click Register. On the Overview page, copy the Application (client) ID (the client id) and the Directory (tenant) ID.
  5. Client secret. Go to Certificates & secrets → Client secrets → New client secret, choose an expiry, click Add, and copy the secret's Value (not its Secret ID) right away. Put a reminder in your calendar: when it expires, create a new one and paste it into SourceLace.
  6. Issuer URL. https://login.microsoftonline.com/<Directory (tenant) ID>/v2.0. It must contain your directory's id: /common or /organizations will not work, because SourceLace only accepts people from your own directory.
  7. Email claim. Go to Token configuration → Add optional claim, choose token type ID, tick email, and click Add (accept the prompt to turn on the Microsoft Graph email permission). Each person's Email field in Entra must hold their address at your domain. Entra does not send email_verified; SourceLace relies on the token coming from your own directory and the address being at one of your SSO domains.
  8. API permissions. The defaults (User.Read, plus openid, email and profile) are enough. If your organization requires it, click Grant admin consent.
  9. Groups (only for group sync).
    • Go to Token configuration → Add groups claim. Choose Groups assigned to the application (recommended) or Security groups. Under ID, keep Group ID. Click Add.
    • If you chose Groups assigned to the application, go to Enterprise applications → SourceLace SSO → Users and groups and add the groups SourceLace should see (this needs Entra ID P1 or higher).
    • Entra sends group object ids (such as 0f3a6c1e-...). In SourceLace, set each group's sync id to the Entra group's Object Id (from Groups → All groups → the group).
    • If someone is in more than 200 groups, Entra leaves the groups out of the token ("group overage"). SourceLace then leaves that person's groups unchanged for that sign-in. Assigning only the needed groups to the application avoids this.

Set up Auth0

Auth0 is a sign-in service. You create one application in it, and SourceLace uses that application to check each person's sign-in. Auth0's own documentation is at auth0.com/docs.

Who: someone with an admin role on your Auth0 tenant (your Auth0 account's own space; its name is shown at the top of the Auth0 Dashboard).

  1. Sign in to the Auth0 Dashboard and choose the tenant your people use.
  2. Go to Applications → Applications → Create Application.
  3. Enter Name: SourceLace. Choose Regular Web Applications (the type with a client secret; a Single Page Web Applications or Native app does not work) and click Create.
  4. Open the application's Settings tab. Under Basic Information, copy:
    • Domain, such as corvanta.us.auth0.com,
    • Client ID,
    • Client Secret.
  5. Scroll to Application URIs. Paste the redirect URL from Before you start into Allowed Callback URLs, exactly, with nothing after it. Leave the other URL boxes empty. Click Save Changes at the bottom of the page.
  6. Issuer URL. Type https://, then your Domain, then a final /, such as https://corvanta.us.auth0.com/. To check it, open https://<your Domain>/.well-known/openid-configuration in a browser. Its issuer line must match what you typed, slash included.
  7. Email. Nothing to add to the application: SourceLace asks for the email scope, and Auth0 sends the address and whether it is verified. Check that each person's email is verified in Auth0: User Management → Users, then open the person. Auth0 sends a verification email to an address that is not yet verified.
  8. Groups (only for group sync). Auth0 sends no groups unless you add them with an Action, a short script Auth0 runs at each sign-in (Actions → Library, then add it to the Login flow). Auth0 requires custom claim names to be full web addresses, for example https://corvanta.com/groups. Enter that full name under Group claim in SourceLace. Auth0's plan may limit Actions; check the Auth0 plan page first.

Then save the Domain-based issuer URL, the Client ID and the Client Secret in SourceLace, as described in Turn it on in SourceLace.

Check that it worked: on the sign-in page choose Continue with SSO / work email and enter a work address at one of your SSO domains. The person signs in through Auth0 and comes back signed in. They then appear on the People page, joined by "Single sign-on".

Auth0's plan: this chapter does not state Auth0's plan limits. Check your plan on the Auth0 billing page before you add more people.

When something goes wrong with Auth0

Auth0 shows its own messages on its pages. The exact wording can differ slightly.

What you see What to do
"Callback URL mismatch." (on Auth0's page) The redirect URL in Allowed Callback URLs is not exactly SourceLace's. Copy it again from Before you start (step 5).
"Invalid state." (on Auth0's page) The sign-in took too long, or the page was reloaded. Start again from SourceLace.
"Unauthorized" or "access denied" (on Auth0's page) The person is blocked in Auth0, or the connection they use is not turned on for the SourceLace application. Check the application's Connections tab.
"Your identity provider has not verified this email address." Verify the person's email in Auth0 (step 7).
"The identity provider's discovery document names a different issuer..." The issuer URL must match the issuer line in the discovery document exactly, slash included (step 6).
"Your identity provider did not send an email address..." The connection the person signs in with must provide an email address. Check its attributes in Auth0.
"Your identity provider did not accept the sign-in..." The Client ID or Client Secret in SourceLace does not match the Auth0 application. Copy both again from Settings.

Set up SAML 2.0

In the SourceLace app, open Sign-in, the Single sign-on tab, and choose SAML 2.0. The screen shows what to give your identity provider:

  • Entity id (also called Audience URI, Identifier or SP entity ID). It has the form https://mcp.sourcelace.ai/saml/<your organization id>/metadata; copy yours from the screen.

  • ACS URL (also called Single sign-on URL, Reply URL or Assertion Consumer Service URL), with the HTTP-POST binding. On this server:

    https://sourcelace.ai/login/saml/acs
    

    If the screen lists more than one address, register all of them.

  • Metadata URL: the same address as the entity id. Identity providers that read SP metadata (Entra, ADFS) can take everything from it.

In your identity provider, send the person's email address as the NameID (format emailAddress), sign the assertion (or the response) with SHA-256, and do not encrypt the assertion. Then give SourceLace your identity provider's details in one of three ways: paste its metadata XML, give its metadata URL, or enter its entity id, single sign-on URL and signing certificate by hand. Tick your email domains and save, then test as in Turn it on in SourceLace.

  • Okta: Applications → Create App Integration → SAML 2.0. Single sign-on URL = the ACS URL (tick Use this for Recipient URL and Destination URL), Audience URI = the entity id, Name ID format = EmailAddress, Application username = Email. For group sync, add a Group Attribute Statement named groups, filter Matches regex .*. Copy the Metadata URL from the app's Sign On tab into SourceLace.
  • Microsoft Entra ID: Enterprise applications → New application → Create your own application → Single sign-on → SAML. Identifier = the entity id, Reply URL = the ACS URL. Under Attributes & Claims, set the Unique User Identifier (Name ID) to user.mail with format Email address. For group sync, add a group claim and set Groups attribute in SourceLace to http://schemas.microsoft.com/ws/2008/06/identity/claims/groups. Copy the App Federation Metadata Url into SourceLace.
  • Google Workspace: Apps → Web and mobile apps → Add custom SAML app. Download the IdP metadata and paste it into SourceLace. ACS URL and Entity ID from SourceLace; Name ID format EMAIL, Name ID the primary email. Turn the app on for your users.
  • ADFS: Add Relying Party Trust, importing SourceLace's metadata URL. Add a claim rule sending E-Mail-Addresses as the Name ID (format Email). In SourceLace use https://<your ADFS host>/FederationMetadata/2007-06/FederationMetadata.xml.
  • OneLogin and JumpCloud: create a custom SAML app with the entity id as audience, the ACS URL as recipient and ACS URL, the email as NameID, and the assertion signed; then paste its metadata into SourceLace.

When your identity provider renews its signing certificate, paste the new metadata (or save again with the metadata URL) while it lists both the old and the new certificate; SourceLace accepts any of the certificates you saved.

Email attribute

SourceLace reads the person's email address from the NameID. If your identity provider sends the email in an attribute instead, enter that attribute's name (such as email) under Email attribute in SourceLace. Leave it empty to use the NameID.

How SourceLace checks a SAML sign-in

Sign-in always starts at SourceLace: sign-ins started from your identity provider's app portal are refused. SourceLace accepts a response only when:

  • it is signed (the response or the assertion) with one of the certificates you saved, using SHA-256 or stronger. Certificates sent inside the response are never trusted;
  • it holds exactly one assertion, and the signature covers exactly that element. SourceLace reads only the signed copy, so extra or moved copies of an assertion ("signature wrapping") never count;
  • its issuer is your identity provider, its audience is your organization's entity id, its recipient and destination are SourceLace's ACS URL, and it answers the very request this sign-in made (each request is accepted once, within ten minutes);
  • it is within its validity times, allowing 90 seconds of difference between clocks;
  • its assertion ID has not been used before (a copied response cannot be replayed);
  • it has no DTD or entity declarations and is not encrypted (SourceLace does not ask for encrypted assertions; the connection is already encrypted).

SAML needs no secret in SourceLace: your identity provider's certificate and addresses are public information.

Other providers

For Google Workspace, OneLogin, Ping, JumpCloud and others with OpenID Connect: create an OpenID Connect web application in the provider's admin console with the redirect URL from Before you start, and note its issuer URL, client id and client secret. Choose the application type called Regular Web Application (some providers call it a confidential client, or just Web application): it is the type that has a client secret. A single-page or mobile application type does not have one and will not work. Allow the standard scopes openid, email and profile. The issuer URL is the address before /.well-known/openid-configuration in the provider's discovery URL. For Google Workspace it is https://accounts.google.com (create an OAuth client of type Web application in Google Cloud Console). Make sure the provider sends the email claim; for group sync, a claim listing the person's groups (set its name under Group claim in SourceLace if it is not groups).

Turn it on in SourceLace

  1. In the SourceLace app, as an admin, open Sign-in and its Single sign-on tab.
  2. Enter the Issuer URL, Client id and Client secret from your identity provider (or, with SAML 2.0, its metadata: see Set up SAML 2.0).
  3. Tick the email domains that should sign in through SSO.
  4. Leave Require SSO off for now, and click Save SSO settings. SourceLace checks the issuer URL by fetching its discovery document; if that fails, it tells you why.
  5. Test it: sign out, choose Continue with SSO / work email on the sign-in page, and enter your work email. You should land in SourceLace, signed in. Try it from an MCP client too if you use one.
  6. Require SSO (optional): back in Sign-in → Single sign-on, turn on Require SSO and save. SourceLace only lets you do this once you yourself are signed in through SSO, so a setting that does not work cannot lock you out.
  7. Group sync (optional): see below.

Your SourceLace contact may already have sent your identity provider's admin the redirect URL, and can see whether the issuer, the client id and the client secret have been saved. Only you enter the client secret: SourceLace's own staff never see it, and it is never shown again once saved.

To turn SSO off, click Turn off SSO. People then sign in with Google or Microsoft again.

If your identity provider stops working while Require SSO is on, your admins cannot sign in either. Contact support@sourcelace.com: the people who run SourceLace can turn Require SSO off for your organization so everyone can sign in with Google or Microsoft again. They must give a reason, which is recorded in your audit trail, and your admins see a note on Sign-in → Single sign-on saying who turned it off, when and why. Turn Require SSO back on yourself once your identity provider works again; the note then goes away.

Group sync

  1. Open the group on the Groups page and, on its Settings tab, set the Sync id: the Okta group name, or the Entra group's object id.
  2. In Sign-in → Single sign-on, turn on Sync groups at each sign-in (the group claim is usually groups) and save.

People's groups update the next time they sign in through SSO. Only groups with a sync id are synced. They show as Synced from Okta / Entra and their people cannot be edited in SourceLace; groups without one show as Made here, are managed by hand and never touched. To use the synced groups for access, turn on access by group.

SCIM provisioning

Status: New. It follows the SCIM 2.0 standard and is tested with the requests Microsoft Entra ID and Okta send, but has not yet been tried with every identity provider's live service. Tell support@sourcelace.com when you set it up so we can watch your first sync with you.

SCIM lets your identity provider (Microsoft Entra ID, Okta or Ping Identity) manage who is in SourceLace for you:

  • New people are added as soon as you assign them to SourceLace in your identity provider, before they ever sign in. They join as members.
  • Profile details stay up to date: name, job title, department and manager. If someone's email address changes, they move to the new address with their role and groups.
  • People who leave lose access at once. When your identity provider deactivates someone or removes them from SourceLace, see When someone leaves.
  • Groups are pushed in bulk and become SourceLace access groups, with their members kept in step as people change roles. See Groups and access.

SCIM is part of the Business and Enterprise plans (see Plans and limits). It works with or without single sign-on: people can keep signing in with Google or Microsoft, or through SSO.

Set up SCIM in SourceLace

  1. In the SourceLace app, as an admin, open Sign-in and its Provisioning (SCIM) tab.
  2. Copy the SCIM base URL. It ends in /scim/v2.
  3. Click Create token and copy the token straight away. SourceLace shows it only once and keeps only a scrambled (hashed) copy, so nobody, SourceLace staff included, can read it back. If you lose it, create another.
  4. Give the base URL and the token to your identity provider, as below.

You can have two tokens at a time. To replace one (for example every year, or when someone who knew it leaves): create a replacement, put it in your identity provider, check that its Last used time moves, then Revoke the old one. A revoked token stops working at once. Each token works only for your organization.

Set up SCIM in Microsoft Entra ID

You need Microsoft Entra ID P1 or P2 (Microsoft's requirement for automatic provisioning).

  1. In the Microsoft Entra admin center, open Enterprise applications. Use the SourceLace app you made for single sign-on, or choose New application → Create your own application and pick the option for an application not in the gallery.
  2. Open Provisioning, and set the provisioning mode to Automatic.
  3. Under Admin credentials, set Tenant URL to the SCIM base URL followed by ?aadOptscim062020 (this tells Entra to follow the SCIM standard more closely), and Secret Token to your SCIM token. Click Test Connection.
  4. Under Mappings, keep Provision Microsoft Entra ID Users and Provision Microsoft Entra ID Groups on. Check that the person's work email (usually mail) is mapped to emails[type eq "work"].value: SourceLace uses it as their address. Without it, SourceLace uses userName (the user principal name), which must then be their email address.
  5. Under Users and groups, assign the people and groups who should use SourceLace. Keep the scope to Sync only assigned users and groups.
  6. Set Provisioning Status to On and save. Use Provision on demand to try one person straight away; after that, Entra syncs about every 40 minutes.

Set up SCIM in Okta

  1. In the Okta Admin Console, open your SourceLace app integration and, on its General tab, turn on SCIM provisioning. Without an app yet, add SCIM 2.0 Test App (OAuth Bearer Token) from the app catalog.
  2. On Provisioning → Integration, set the SCIM connector base URL to the SCIM base URL, the Unique identifier field for users to userName, and the authentication mode to HTTP Header, with your SCIM token. Tick Push New Users, Push Profile Updates and Push Groups, then click Test Connector Configuration and save.
  3. On Provisioning → To App, enable Create Users, Update User Attributes and Deactivate Users.
  4. Assign people and groups on Assignments, and choose the groups to send on Push Groups.

Okta sends each person's username as userName: it must be their email address (it is, unless your Okta usernames are not email addresses).

Set up SCIM in Ping Identity

  1. In PingOne, open Integrations → Provisioning and add a new connection of type SCIM Outbound.
  2. Set the SCIM base URL to the SCIM base URL, the authentication method to OAuth 2 Bearer Token with your SCIM token, and the user identifier to userName. Allow creating, updating, disabling and removing users.
  3. Add a provisioning rule for the people and groups who should use SourceLace, map their email address to userName and to the work email, and turn the rule on.

PingFederate can provision through its own SCIM outbound connector with the same base URL and token.

What SourceLace keeps

For each person: their email address, the id and username your identity provider uses for them, and their name, job title, department, employee number and manager's id, as your identity provider sends them. Nothing else (no passwords: identity providers that send one, such as Okta's test app, have it ignored). Other details, such as phone numbers or addresses, are accepted and not kept.

When someone leaves

When your identity provider deactivates someone, or unassigns them from SourceLace, SourceLace, at that moment:

  • stops them signing in, and ends their open sessions in the SourceLace app;
  • deletes their connections from AI apps (MCP clients): those apps would have to sign in again, and cannot;
  • deletes their sign-ins to your sources, so nothing is kept that could act for them;
  • pauses the AI agents they own and stops their waiting runs, for an admin to decide on: delete them, or keep them for when the person comes back (the owner can then resume them);
  • frees their seat.

They stay on the People page, marked deactivated, so they cannot come back in through your email domain. When your identity provider deletes them for good (Entra does so 30 days after a person is removed), they are removed from SourceLace too, unless their email domain is one your people join by: then they stay listed as deactivated. Reactivating someone in your identity provider lets them sign in again. Every one of these changes is in your audit log.

Groups and access

Each group your identity provider pushes becomes a SourceLace access group with the same name, and its members are kept in step: someone added to or removed from a group in your identity provider has that access from their next request in SourceLace. Group names must be unique, ignoring case.

  • A pushed group gives no access by itself. You decide what each group may use on the Groups page (see Access by group). SCIM never changes what a group may use, so it can never give anyone more than you allowed.
  • Groups you already made are reused. When your identity provider pushes a group with the same name as one you made by hand, SourceLace links the two, so the access you set up applies at once. People you added to that group by hand stay in it.
  • Deleting a group in your identity provider deletes it in SourceLace if SCIM made it; a group you made yourself goes back to being managed by hand, without the people SCIM put in it. It shows as Made here again, so you can change its people, unless you had given it a sync id yourself (for group sync): then it keeps that sync id.
  • With group sync at sign-in also on, groups that SCIM manages follow SCIM, which is always up to date; sign-in group sync handles the others.

Roles and the admin group

SCIM adds everyone as a member, and never makes anyone an admin by itself. To have your identity provider decide who your admins are, choose one pushed group as the Admin group in Sign-in → Provisioning (SCIM):

  • people your identity provider puts in that group become admins;
  • they go back to members when they leave the group;
  • admins you made by hand are never made members by SCIM, and your last admin is always kept.

SCIM questions

Do I need single sign-on to use SCIM? No. SCIM decides who is in SourceLace; people still sign in with Google, Microsoft or SSO.

Which identity providers work? Microsoft Entra ID, Okta and Ping Identity (PingOne and PingFederate), with the steps above. Others that support SCIM 2.0 with a bearer token should work too; tell support which one you use.

What does the identity provider send, and what does SourceLace answer? Standard SCIM 2.0: users (with the enterprise extension for department and manager) and groups, created, read, updated, replaced and deleted, with filters such as userName eq "ana@corvanta.com", pages of up to 500 results, and versions (ETags). Bulk requests and sorting are not offered; identity providers do not need them.

Is there a limit on requests? Yes, a generous one per organization (1,200 a minute unless your SourceLace contact changes it). Above it SourceLace answers "try again later", and identity providers retry by themselves.

What if the token leaks? Revoke it in Sign-in → Provisioning (SCIM): it stops working at once. Revoking is allowed on any plan. The token can only change your own organization's people and groups, and every change it makes is in your audit log.

Where do I see what SCIM changed? In the Audit log: every change is listed (scim_user_create, scim_user_deactivate, scim_group_members and so on), showing the token it came through (its first letters), the person or group, and what changed. Only which details changed is recorded, never their values.

Can I change a deactivated person by hand? You can remove them on the People page. To let them back in, reactivate them in your identity provider.

Switching to another identity provider

When your company moves to another identity provider (for example from Okta to Microsoft Entra ID), an admin starts the change Switch single sign-on provider under Changes (see Changes). It lists the steps in order and ticks each off when SourceLace sees it done:

  1. Set up the new provider in SourceLace. Your identity provider's admin registers SourceLace in the new provider as described in Set up Okta, Set up Microsoft Entra ID or Set up SAML 2.0. Then you enter the new details in Sign-in → Single sign-on and save. SourceLace sees the save.
  2. Sign in through the new provider. Sign out, then sign in again with your work email. SourceLace sees the sign-in through single sign-on. If it fails, see When something goes wrong.
  3. Remove SourceLace from the old provider. Your identity provider's admin deletes SourceLace's app or registration in the old provider, so nobody can sign in through it. SourceLace can't see the other product, so you confirm this step.

People keep their chats, groups and access: SourceLace knows them by their email address, not by their provider. If you use SCIM, set it up in the new provider too (see SCIM provisioning).

When something goes wrong

What you see What to do
"Enter the issuer URL your identity provider shows, such as https://corvanta.okta.com." The issuer URL is empty or not an https:// address. Copy it from your identity provider.
"The identity provider's discovery document names a different issuer..." Copy the issuer URL exactly as your provider shows it. For Entra, use the one with your directory's tenant id, not /common or /organizations.
"... does not sign in to SourceLace with single sign-on. Go back and sign in with Google or Microsoft..." That email domain is not ticked under SSO, or the domain is not on your People page.
"Your identity provider did not accept the sign-in..." Check the client id, client secret and redirect URL in both your identity provider and SourceLace. An expired Entra client secret causes this too.
"Your identity provider did not send an email address..." Add the email claim to the SourceLace app in your identity provider (for Entra, step 7 above).
"Your identity provider has not verified this email address." The provider sent email_verified: false. Verify the address in your identity provider.
"... is not at a domain your organization signs in with through SSO." The person's address in the identity provider is at a domain not ticked for SSO in SourceLace.
"... already uses SourceLace with another organization, so it cannot sign in here." That address belongs to another SourceLace organization. Contact support.
"The sign-in was not meant for SourceLace. Ask your admin to check SSO." The token's audience or issuer does not match the client id or issuer saved in SourceLace.
"Single sign-on is no longer set up for your organization." SSO was turned off while the person was signing in. Sign in with Google or Microsoft, or turn SSO back on.
"Your identity provider's answer is not signed with the certificate SourceLace has." Your identity provider renewed its signing certificate, or signs with SHA-1. Save its current metadata in SourceLace, and set the signature to SHA-256.
"Your identity provider encrypted the assertion..." Turn off assertion encryption for SourceLace in your identity provider.
"Your identity provider did not send an email address in the NameID..." Send the email address as the NameID (format emailAddress), or name the attribute holding it under Email attribute.
"The sign-in was not meant for SourceLace (the audience is different)." The entity id (audience) in your identity provider must be exactly the one SourceLace shows.
"The sign-in was not meant for this request..." The ACS URL (recipient) in your identity provider must be exactly the one SourceLace shows. Start the sign-in from SourceLace, not from your identity provider's app portal.
"This sign-in has expired or was already used." More than ten minutes passed, or the page was reloaded. Start again from SourceLace.
SCIM: "The SCIM token is missing, wrong or revoked." Create a token in Sign-in → Provisioning (SCIM) and paste the whole token into your identity provider.
SCIM: "SCIM provisioning is not available to this organization" Your plan does not include SCIM, or it is not turned on for your organization yet. Ask your SourceLace contact.
SCIM: "SourceLace needs an email address" Map the person's work email to emails[type eq "work"].value, or make userName their email address.
SCIM: "... cannot be provisioned in this organization." That address already uses SourceLace with another organization. Contact support.
SCIM: "Your ... plan allows at most ... people" Every seat is used. Free a seat, or ask your SourceLace contact for more.
Someone's groups did not change Group sync only runs at an SSO sign-in, and only for groups with an external id. For Entra, check the person is in fewer than 200 groups, or assign only the needed groups to the app.