> For the complete documentation index, see [llms.txt](https://docs.unimarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unimarket.com/documentation/troubleshooting/troubleshooting-sso-errors.md). # Troubleshooting SSO Errors SSO errors typically occur when there is a mismatch between your organization's Identity Provider (IdP) and Unimarket (the Service Provider). Most issues can be resolved by verifying user attributes or checking account status within Unimarket. For background on setting up the integration, see [Setting Up SAML SSO](/documentation/authentication-and-users/setting-up-saml-sso.md). ## "The Authentication Service configured for your Community did not authenticate you" **Example of exact error:** > Single Sign-On request to Unimarket failed. The Authentication Service configured for your Community did not authenticate you or did not return a valid response. Please try again or contact your administrator. ![](https://help.unimarket.com/hc/article_attachments/58390096963865) **Cause:** The IdP is sending an incomplete or malformed SAML assertion. This often means mandatory attributes (like email or NameID) are missing or the user's local profile is corrupted. {% hint style="info" %} This is usually not an issue on the Unimarket side, unless a new development has rolled out. {% endhint %} **Troubleshooting Steps:** * **Browser Cleanup:** Have the user clear cache/history or try an Incognito/Private window to rule out stale session cookies. * **IT Review:** Ask your IT team to verify the user's attributes in the IdP (Active Directory/Okta/Azure). * **Unimarket Support:** If the issue persists, provide Unimarket Support with the user's name and a precise timestamp to check the integration logs. ## "Auto-Provisioning not enabled" **Sample of exact error:** > Single Sign-On request to Unimarket failed. Auto-Provisioning not enabled **Cause:** Unimarket receives a valid login but cannot find a matching user record, and the system is not configured to create new users automatically. **Troubleshooting Steps:** * Check inside Unimarket to confirm if the user login has been created. * If user login credentials have been created, compare the SSO username and the Unimarket username to ensure they are exactly the same. * If the username is **not** the same, make updates. * If the username **is** the same, reach out to the Unimarket Support team with the following information: * The SSO username * The Unimarket username * Date and time stamp when the user last attempted login ## "Your account has been locked" **Sample of exact error:** > Your account has been locked. Contact your support person to unlock it, then try again. ![](https://help.unimarket.com/hc/article_attachments/45852270743449) **Cause:** The user's Unimarket profile has been locked due to security overrides. **Troubleshooting Steps:** * **Admin Check:** Go to the **Administration** module > **Users**, clear the **State** filter, and select **Apply Filter**. * **Re-enable:** If the state is Disabled, edit the profile to Enabled. Once completed, ask the user to attempt logging into Unimarket. * **Lockout:** If locked, verify the user hasn't been attempting to log in via the standard Unimarket login page instead of the SSO portal. If the above does not resolve the matter, reach out to your IT team to check the SAML setup for the user to determine if the user is logging into Unimarket via Single Sign-On. ## "The user account is disabled. Please contact your Administrator" **Sample of exact error:** > Single Sign-On request to Unimarket failed. The user account is disabled. Please contact your Administrator. ![](https://help.unimarket.com/hc/article_attachments/45852271120921) **Cause:** The user's Unimarket profile has been manually disabled. **Troubleshooting Steps:** * **Admin Check:** Go to the **Administration** module > **Users**, clear the **State** filter, and select **Apply Filter**. * **Re-enable:** If the state is Disabled, edit the profile to Enabled. Once completed, ask the user to attempt logging into Unimarket. If the user login is in an enabled state, reach out to the Unimarket Support team with the following information: * The user's first and last name * Date and time stamp when the error occurred ## "Authentication Service Error" **Sample of exact error:** > Single Sign-On request to Unimarket failed. Authentication Service Error ![](https://help.unimarket.com/hc/article_attachments/58390096965785) **Cause:** The IdP is sending an incomplete or malformed SAML assertion. This often means mandatory attributes (like email or NameID) are missing or the user's local profile is corrupted. **Troubleshooting Steps:** * **Browser Cleanup:** Have the user clear cache/history or try an Incognito/Private window to rule out stale session cookies. * **IT Review:** Ask your IT team to verify the user's attributes in the IdP (Active Directory/Okta/Azure). * **Unimarket Support:** If the issue persists, provide Unimarket Support with the user's name and a precise timestamp to check the integration logs. ## "Missing data" **Sample of exact error:** > Single Sign-On request to Unimarket failed. Missing data ![](https://help.unimarket.com/hc/article_attachments/45852271651481) **Cause:** The IdP is sending an incomplete or malformed SAML assertion. This often means mandatory attributes (like email or NameID) are missing or the user's local profile is corrupted. **Troubleshooting Steps:** * **Browser Cleanup:** Have the user clear cache/history or try an Incognito/Private window to rule out stale session cookies. * **IT Review:** Ask your IT team to verify the user's attributes in the IdP (Active Directory/Okta/Azure). * **Unimarket Support:** If the issue persists, provide Unimarket Support with the user's name and a precise timestamp to check the integration logs. ## Troubleshooting Checklist for IT Admins If a specific group of users is failing, check the following technical configurations: * **SAML Certificate:** Check if your IdP signing certificate has recently expired. * **Clock Skew:** Ensure your IdP server time is synchronized via NTP; a difference of more than a few minutes will cause the SAML assertion to be rejected. * **Encryption:** Verify if Unimarket expects an encrypted vs. unencrypted assertion. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.unimarket.com/documentation/troubleshooting/troubleshooting-sso-errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.