> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connectly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting and maintenance

> Fix common enterprise SSO and SCIM errors, and keep the connection running after go-live

When something fails, send Connectly the full address bar URL and the time: its `error` part names the cause.

***

## Common errors

| What you see | Why | Fix |
| - | - | - |
| With SCIM: Connectly shows `error=jit_disabled` after the sign-in | The account that signed in was never provisioned to Connectly. Most often the browser was already signed in to your identity provider as someone else, usually the admin. | Use a private window or another browser profile. Signing out of Connectly does not sign you out of your identity provider. Check the person is assigned and provisioned. |
| Without SCIM: "Sign-in was not completed" with `error=access_denied` | Most often no Owner added the account that signed in, or the browser was already signed in to your identity provider as someone else. | Use a private window or another browser profile. Check that an Owner added the person under **Settings** → **Users**, with the email your identity provider sends. If it still fails, send Connectly the URL. |
| A provisioned person still gets `error=jit_disabled` | The SAML Name ID and the SCIM `userName` send different values. | Send the same sign-in name in both, then provision the person again. |
| Provisioning succeeds, but the person is not in Connectly | Connectly could not accept them: their email is empty or not on your verified domain, or Connectly has not switched provisioning on for your business yet. | Send an email address (or the sign-in name as email), or ask Connectly to verify the domain or switch provisioning on. Then provision them again. |
| Connectly shows "Sign-in was not completed" | Connectly's page for any sign-in that did not finish. | Send Connectly the URL; its `error` part says why. |
| The SCIM connection test fails | The endpoint is wrong, or the token was revoked. | Paste both again. If the token was revoked, ask Connectly for a new one or a new setup link. |

### Microsoft Entra

| What you see | Why | Fix |
| - | - | - |
| Microsoft error `AADSTS50105` | The person is not assigned to the application. | Assign them in **Users and groups**. |
| Microsoft error `AADSTS700016` or `AADSTS50011` | The Identifier or the Reply URL differs from Connectly's value. | Copy both again from the wizard or from Connectly's values, with no spaces. |
| Entra says groups are not available for assignment | Entra ID Free. | Assign people one by one, or use Entra ID P1 or P2. |

***

## After go-live

* **New people:** assign them to the application. The next provisioning cycle adds them, or provision them on demand. Without SCIM, an Owner also adds them in Connectly.
* **People who leave:** unassign or disable them in your identity provider. With SCIM, the next cycle removes their Connectly access. Without SCIM, also remove them in Connectly.
* **Signing certificate:** your identity provider's SAML signing certificate expires (three years by default in Microsoft Entra). Before it does, agree a time with Connectly: you make the new certificate active and send its metadata, and Connectly loads it at the same time.
* **SCIM token:** it does not expire. Replace it as described in [The SCIM token](https://docs.connectly.ai/enterprise-sso/saml-and-scim-settings.md#the-scim-token) whenever your policy asks, or when someone who saw it leaves.
* **Another email domain:** ask Connectly. Each domain is verified the same way as the first.
* **Switching it off:** stop provisioning in your identity provider and tell Connectly, who turns off sign-in through your connection.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.