I am in the process of trying to setup an express based API server, using keycloak-connect, with a vue based front-end. This is proving challenging with most errors being fairly opaque.

This is where it would be useful for keycloak-connect to support a verbose mode, so see what was sent to the server and the internal failure modes of the package. Right now I am left editing the code and adding my own logger output at key locations.

The main area of interest is GrantManager.prototype.validateToken, where the failure reason is swallowed and not made available to the downstream consumers - it is not logged anywhere either. It took me a good while for this reason to find the internal failure reason was 'invalid token (wrong audience)', instead of being presented in a way I could quickly look up resolution approaches.

If this feature already exists, then I am having a hard type finding documentation on the option the keycloak-connect constructor accepts.