How to stop node-oauth2-jwt-bearer from polluting my output about node-oauth2-jwt-bearer HOT 5 CLOSED

Hi @rococtz - thanks for raising this

All this package's errors are caught and handled by Express (see https://github.com/auth0/node-oauth2-jwt-bearer/blob/main/packages/express-oauth2-jwt-bearer/src/index.ts#L76)

This is how errors should be handled in Express, see https://expressjs.com/en/guide/error-handling.html#catching-errors

I'm not sure what mechanism is causing those entries to show in your Cloudwatch logs, perhaps it's the default Express error handler - is your NODE_ENV set correctly? Also, you could have a look at writing your own error handler

from node-oauth2-jwt-bearer.

@adamjmcgrath This is very helpful, thank you very much.

from node-oauth2-jwt-bearer.

@rococtz @adamjmcgrath I've seen identical InvalidTokenError: "exp" claim timestamp check failed errors, despite my JWTs being set to a 30 day expiry (in the Auth0 dashboard).

For my user base, this means that expired tokens should almost never happen, yet I see these errors many times per day.

Any hints as to how these errors can be debugged? As @rococtz hints at, even reqs without a token end up spitting out "exp" claim timestamp check failed, so I have a feeling this error block is unintentionally catching many other errors.

I've tried logging the WWW-Authenticate header as per the docs. It's just:

{"WWW-Authenticate":"Bearer realm=\"api\", error=\"invalid_token\", error_description=\"'exp' claim timestamp check failed\""}

Which doesn't actually provide any further information.

from node-oauth2-jwt-bearer.

Hi @isaachinman

As @rococtz hints at, even reqs without a token end up spitting out "exp" claim timestamp check failed, so I have a feeling this error block is unintentionally catching many other errors.

I don't think that's what they're saying. And I don't see how this would be possible since UnauthorizedError will be thrown if there is no token on the request, and the part of code that validates the claims will not be reachable.

If you think there is a bug with this SDK, could you raise a new issue and share an example repo that demonstrates the bug and I'd be happy to debug it.

from node-oauth2-jwt-bearer.

@isaachinman I was getting the expired token error because it was truly expired :) The error was relevant so my only issue was that I was not catching the right way which is by using next().

from node-oauth2-jwt-bearer.