← ClaudeAtlas

401-from-verifytoken-even-though-the-u-aec393a46103f475listed

Your backend rejects a session token the frontend just minted. The usual cause is a stale or wrong JWKS public key, not a broken session. Check the key before you touch auth code.
Vectle/skills · ★ 0 · API & Backend · score 65
Install: claude install-skill Vectle/skills
**TL;DR:** Your backend rejects a session token the frontend just minted. The usual cause is a stale or wrong JWKS public key, not a broken session. Confirm the cause 1. Decode the token header (base64, no verification needed) and compare its kid to the key your backend uses. ## The fix 1. Figure out which verifier you call. `authenticateRequest` is networkless only when you pass `jwtKey` (the JWKS public key from the dashboard). Without it, the SDK makes a network call to fetch the JWKS; blocked egress or a stale cache then looks like a bad token. 2. If you pass `jwtKey`, confirm it is the CURRENT public key for THIS instance. Keys copied long ago, or copied from a different instance, fail signature verification silently. 3. Decode the token header (base64, no verification needed) and compare its `kid` to the key your backend uses. A mismatch after a key rotation is the classic cause. 4. Make sure you are not verifying a JWT-template token as a session token (or the reverse). Template tokens carry different claims and issuers. 5. Re-copy the JWKS public key from the dashboard into your `jwtKey` config and redeploy. 6. If you fetch the JWKS over the network, clear the cached keys and let the SDK refetch. 7. Always pass `authorizedParties` with your real origins alongside the key (see the azp skill). ## When to use this - This covers exactly what the title says: 401 from verifyToken even though the user is signed in. - You are setting this up for the first time, or a