TL;DR
Signature verification failed is one message for several causes: a different key (a one-byte difference is enough), a tampered payload, or the wrong algorithm family.
Expired, not yet valid, audience, issuer and missing-claim failures each raise their own exception class, so the class tells you which claim to check.
jwt.decode(token, options={"verify_signature": False}) returns a tampered {'role': 'admin', ...} payload as if nothing happened. Keep it out of request paths.
Your login works on your laptop. In prod every request dies with InvalidSignatureError: Signature verification failed , and you start doubting the signature. We got that exact text from a token signed with a different key, and again from a token whose payload we edited by hand. The message can't tell you which one you have.…