When i select RS256 algorithm under jwt.io , signature validation fails when i add “crit”:[“exp”] . It is working with “exp” alone without “crit” field. What is the reason ? Any help is great. Thank you { “typ”: “JWT”, “alg”: “RS256”, “exp”:1593796130, “crit”:[“exp”] }

Hey there! Let me talk it over with the jwt.io maintainers and get back to you soon!

Hey there, Sorry for the dleay in response I got the message from JWT.io maintainers but forgot to relay it. JWT.io uses node-jose under the hood and this is where the issue is potentially coming from.

Jwt.io debuger debugger error when "crit"field is added in header

Get Help

nandh1 July 26, 2020, 5:11pm 4

Hello any update on this?

Invalid signature when adding "crit" to header

Topic		Replies	Views
Invalid signature when adding "crit" to header JWT.io	3	4280	August 17, 2020
"alt": "none" validation bug on jwt.io Get Help vulnerability	1	4100	June 23, 2017
Couldn't using Signature Algorithm RS256 JWT.io rs256	1	4425	December 19, 2018
Https://jwt.io/ issue JWT.io	1	3189	January 29, 2020
Jwt.io debugger and ESxxx validation JWT.io debugger	0	5153	April 24, 2020

Jwt.io debuger debugger error when "crit"field is added in header

Related topics