Skip to main content

SSO login failing with "Signature verification failed" error

If your JWT-based SSO login is failing with a "Signature verification failed" error this article walks you through what causes the issue and how to resolve it

Updated today

👉Understanding the issue

Sleekplan SSO keys don't expire, so if SSO was working fine before and has suddenly broken, expiry isn't the cause. What's most likely happened is that the SSO key in Sleekplan was accidentally rotated at some point, which means the key your backend is currently using to sign JWT tokens no longer matches the one Sleekplan expects.

📋You can confirm this is the issue by going to Settings › Developer › SSO logs in your Admin dashboard and looking for entries containing "message": "Signature verification failed"

ℹ️How to fix it

The fix is straightforward: rotate the key in Sleekplan to generate a fresh one, then update your backend with the new value.

  1. Head to Settings › Developer › SSO Key in your Sleekplan Admin dashboard.

  2. Click Rotate key. Sleekplan will generate a new SSO key for your account.

  3. Copy the new key and update it in your backend or wherever you sign your JWT tokens.

  4. Test an SSO login. Your users should be able to log in right away

Related Articles
Single Sign-On (SSO)
How to Set Up SSO Between Freshdesk and Sleekplan in 3 steps: No-coding approach
Did this answer your question?