JWT Auth Debugging
Decode a JWT token, verify its signature integrity, and check if the token has expired — a complete auth debugging workflow.
When to Use This Workflow
Debug failing JWT authentication by inspecting token payload, validating the signature, and checking expiration timestamps.
Workflow Steps
JWT Decoder
Decode the JWT token to inspect header and payload claims
Hash Generator
Hash the signature portion to verify integrity against known secret
Timestamp Converter
Convert 'exp' and 'iat' claims from Unix epoch to human-readable dates
Download Workflow Template
Frequently Asked Questions
How do I debug a JWT 401 Unauthorized error?
Start by decoding the JWT to check the payload claims (iss, aud, exp). Then verify the signature matches your secret key using HMAC-SHA256. Finally, convert the 'exp' claim to a readable date to confirm the token hasn't expired.
What are the most common JWT authentication failures?
The top three causes are: expired tokens (exp claim in the past), wrong signing algorithm (alg mismatch), and invalid audience (aud claim doesn't match the server). This workflow checks all three.
Can I use this workflow for RS256 JWTs?
Yes. The decode step works for any JWT algorithm. For RS256, you'll need the public key to verify the signature instead of a shared secret.