Adding minIssuedAt / minTokenDate to JWTVerifyOptions?

[Manouchehri]

Example usage:

const jwt_verified = await jwtVerify(unchecked_jwt_string, pubkey, {
      algorithms: ['ES256'],
      issuer: 'panva.demo.ai.moda',
      audience: 'panva',
      maxTokenAge: '31536000s',
      minIssuedAt: new Date(1672531200000),
      requiredClaims: ['sub', 'jti']
    })

And it would check that the iat is past the minIssuedAt date.

[panva]

I think you should look at the nbf claim.

[panva]

Sorry, I don't see the point. If you know the date you want as minimum then either use the existing maxTokenAge option of passing the seconds elapsed since, or simply evaluate the iat from the verified payload afterwards.

[Manouchehri]

const jwt_verified = await jwtVerify(unchecked_jwt_string, pubkey, {
      algorithms: ['ES256'],
      issuer: 'panva.demo.ai.moda',
      audience: 'panva',
      maxTokenAge: Math.min(Math.floor((Date.now() - new Date("Dec 31 2022 19:00:00").getTime())/1000), 31536000),
      minIssuedAt: new Date(1672531200000),
      requiredClaims: ['sub', 'jti']
    })

True, it feels a bit messy though?

[panva]

If you insist on inlining it, sure, feels ugly. But functional.

[Manouchehri]

If I make a PR for maxTokenAge to accept a Date, will you consider merging it? =)

[panva]

I will not, the name maxTokenAge does not lend itself semantically to accepting a Date object.