JWT token not working after upgrade - [Linux] and [Windows]
If you are using JWT-based SSO in Sisense, upgrading to version 6.7 or later may cause authentication failures. This issue could be linked to a missing "typ": "JWT" attribute in the JWT token header. This guide shows how to detect and fix this issue for both cloud and on-prem deployments. Typ header is still required as of Sisense Version L2025.4.
Step-by-Step Guide
- Confirm the Issue
After upgrading your Sisense, your JWT SSO login might stop working. To check:
-
- Open your browser.
- Open developer tools (usually via F12 or right-click → Inspect).
- Go to the Network tab.
- Locate Your JWT Token
-
- Navigate to your Sisense instance and attempt to log in via SSO.
- In the Network tab, look for the request containing "jwt" in the URL.
- Highlight the request and open the Headers tab.
- Copy the request URL and paste it into a text editor.
Example screenshot
- Decode the JWT Token
-
- Extract the JWT token from the request URL.
- The token is the string between "jwt=..." and "&return...".
Example screenshot
-
- Use a JWT debugger such as jwt.io to decode the token.
- Check the decoded header section for the "typ": "JWT" attribute.
Example header:
{
"alg": "HS256",
"typ": "JWT"
}- Fix the Token Generation
-
- If "typ": "JWT" is missing, update your SSO script to explicitly include it when generating the token.
Example:
// JWT header example
const header = {
alg: "HS256",
typ: "JWT"
};-
- Regenerate the token and reattempt login.
- Verify the Fix
-
- Repeat steps 1–3 to ensure the "typ": "JWT" attribute now exists in the token header.
- SSO login should now work without errors.
Conclusion
A missing "typ": "JWT" attribute in the JWT token header can cause SSO failures after upgrading Sisense. By inspecting the JWT token and updating your SSO script to include this attribute, you can restore SSO functionality quickly.
References/Related Content
- JWT - Debugger Tool
- SSO Using JWT - Sisense Docs
- SSO With JWT | Sisense Developers - Sisense Dev Docs
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
Published 10-06-2025
