user3075978
Reputation: 845
Why are these two generated JWTs different? (jwt.io vs postman)
I am trying to generate a JWT in Postman, and I don't understand why the token generated at jwt.io and Postman are different when Base64 Encoded is selected.
- When the "Secret Base64 encoded" option is disabled, both tokens match.
- When the "Secret Base64 encoded" option is enabled, the tokens are different, even though they are both using the same secret.
Any idea why the tokens would be different when Base64 Encoded is enabled?
Upvotes: 1
Views: 147
Answers (0)
Related Questions
- What is secret key for JWT based authentication and how to generate it?
- Why does my JavaScript code receive a "No 'Access-Control-Allow-Origin' header is present on the requested resource" error, while Postman does not?
- Why do we use Base64?
- In PHP/Laravel, package Firebase/JWT token generation secret base64 encoded invalid signature
- JWT (JSON Web Token) automatic prolongation of expiration
- How to Create a JWT in Java with the secret base64 encoded
- Why can't the google JWT token be decoded by jwt.io
- JWT token generated using jsonwebtoken library gives invalid signature in jwt.io
- Token generated using JWTSigner.sign() saying invalid signature in jwt.io debugger