More error logging and customizable error handling with JWT policy

[anderius]

Is your feature request related to a problem? Please describe.

Some commons errors could be easily solved if the logging or response was improved. For example, we see that many consumers use wrong issuer, or use an recently expired token.

Describe the solution you'd like

It would be very helpful if the reason the token was rejected, was logged with context making it possible to correlate it with the access log.

Sometimes, these error happens so often, that it is desired to give the error message back to the user. In that case, it should be customizable. For example, a list of error codes, and a subset of those that we can choose to expose to the client.

Describe alternatives you've considered

To get some logging, we currently parse and validates the token manually AFTER it is rejected, to catch some common errors. That is not ideal.

Additional context

None.

[github-actions]

Hi @anderius thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!