Don't spam logs with INFO messages by default

Issue #32 resolved
Magnus Andersson created an issue

Hi

First off thank you for a very nice library!

I have an issue with the default logging levels which is actually causing more and more frustration.

Each time org.jose4j.jwa.AlgorithmFactoryFactory gets initialized I get 86 lines of registerAlgorithm log messages.

For application starts that is not a big issue, but we have loads of tests where many relies on jose4j for creation of tokens or validation of tokens. The jose4j library is spamming our logs, making it hard to locate the interesting stuff.

I don't think this information belongs on the info log level, perhaps it could be moved to debug level instead?

I know I can turn off the logging if I dig around and override the logging for that package (will be my next move), but I don't think everyone should have to and I might turn off future logging that I would care about.

I'm using version 0.4.3 of jose4j.

Comments (6)

  1. Brian Campbell repo owner

    The thinking was that initialization would happen once at application startup and this initialization info was maybe useful info to have, which was why I went with info. But it is verbose and your point is taken. Debug may be more appropriate.

  2. Log in to comment