Users have reported intermittent connectivity issues when utilizing the MCP server, specifically following recent updates.
Symptoms include 502 Service Unavailable errors and hanging initialize requests within VS Code and other MCP clients.
These failures occur after approximately one hour of use, even when the generated token’s own expiration timestamp remains valid.
The issue manifests inconsistently, leading to scenarios where a token may function during one session but fail in another.
To remediate the current instability and prevent future occurrences, the following strategies should be implemented based on the specific use case:
For Interactive Users:
sc_admin) to generate tokens. Local accounts are not subject to SAML session states, providing a more reliable and persistent connection.For Automated/API-Only Integrations:
edit_authentication capability) to mint short-lived, user-specific tokens on demand via the /services/authorization/tokens endpoint. This approach decouples the integration from SAML session constraints while ensuring that all actions remain logged under the specific user identity.| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |