Why does the parser pass 'false' as required to the VerifyNotBefore and VerifyIssuedAt? #431
Unanswered
DukeLuke94
asked this question in
Q&A
Replies: 3 comments 1 reply
-
Im guessing this is a bug... I opened a PR to fix it but not sure how to get traction on it |
Beta Was this translation helpful? Give feedback.
1 reply
-
This has come up a few times, have you seen this comment from another related issue? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Oh interesting, I had not seen that. I will see if I can get that
implemented in the way described by the ticket..
Another question about validation, is it intentional that parseUnverified
skips calling Validate() (so my custom claims Validate() method does not
get called if I use ParseUnverified)
…On Thu, Jun 12, 2025 at 1:42 PM Michael Fridman ***@***.***> wrote:
This has come up a few times, have you seen this?
#411 <#411>
—
Reply to this email directly, view it on GitHub
<#431 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWNJFUYRAEJXYCJOMTAH4CD3DHQ3LAVCNFSM6AAAAABVJ4BRMWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNBVGMZDAMY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
If I configure the parser to validate the IssuedAt claim (with parserOptions: jwt.WithIssuedAt) and I provide a jwt token without an "iat" claim, the token is valid. Why? Because the parser passes false as required, as apposed to the other functions such as verifyAudience and verifyIssuer. What's the logic behind this?
`
`
Beta Was this translation helpful? Give feedback.
All reactions