> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/security/identity-providers-sso/resolving-sso-login-issues-when-updating-connection-tokens.md).
# Resolving SSO Login Issues When Updating Connection Tokens
##  Overview
When updating an organization token in Flosum Global Settings, Single Sign-On (SSO) may cause Global Settings to authenticate with the currently logged-in SSO user instead of the designated service user account.
{% hint style="info" %}
#### Best Practice
Flosum strongly recommends using a dedicated service user account, not configured for SSO, to connect Salesforce orgs to any Flosum product.
{% endhint %}
If your **dedicated service user** is not configured for SSO, you may need to adjust the login URL to ensure Global uses the correct account.
## How to Resolve
{% hint style="info" %}
The instructions are written for the Chrome browser, but you may be able to complete the process in another browser. Chrome is recommended.
{% endhint %}
{% stepper %}
{% step %}
### Monitor Network Activity
1. Open your Chrome browser and log in to **Global Settings**.
2. Click the **Three Dots** menu.
3. Click **More Tools > Developer Tools**.
4. Select the **Network** tab.
{% endstep %}
{% step %}
### Update Token
1. Log in to **Global Settings**. See the [Log In To Global Settings](/global-settings/getting-started/log-in-to-global-settings.md) article for more instructions.
2. Click **Connections** from the sidebar menu**.**
3. Click **Update Token** for the connection you want to update.
{% endstep %}
{% step %}
### Capture the Authorization URL
1. Watch for a network entry that begins with **authorize**.
2. As soon as you see it, press **ESC** to stop the browser from refreshing.
3. This prevents the redirect and allows you to capture the login URL.
{% endstep %}
{% step %}
### **Modify the Login URL and Authenticate**
1. Copy the captured URL and paste it into the browser.
2. Replace the custom domain portion with one of the following:
| Salesforce Org Type | Domain |
| ------------------- | -------------------- |
| **Sandbox orgs** | test.salesforce.com |
| **Production orgs** | login.salesforce.com |
3. Keep the rest of the URL unchanged.
4. Press **Enter** to launch the URL.
5. Log in using the dedicated service user’s credentials (not the SSO account).
{% endstep %}
{% step %}
### Confirm Connection Username
1. Return to Global Settings.
2. Click **Connections** from the sidebar menu**.**
3. Verify that the **dedicated service user** now shows under the **Username** for the connected org.
{% endstep %}
{% endstepper %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flosum.com/global-settings/security/identity-providers-sso/resolving-sso-login-issues-when-updating-connection-tokens.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
