I believe the only way to achieve the desired behavior is to make 'log spam' the default behavior and allow us to override it via an option in Shiro's configuration, instead of hard coding log levels.
Brian Demers wrote > There have been a couple issues on either side of this. > > These exceptions should be logged, as 'debug' (if i remember correctly). > Increasing the default logging can cause log spam in the cases where > multiple realms are enabled, and one is misbehaving (db is down, or some > network issue). > > The common (and valid complain) is similar to your as this does not > provide > a good first experience, when setting up Shiro for the first time. > > Does anyone have any ideas on ways to both eliminate the log spam and > provide make it easier to troubleshoot for new installs? -- View this message in context: http://shiro-user.582556.n2.nabble.com/A-ponion-about-org-apache-shiro-authc-AbstractAuthenticator-authenticate-AuthenticationToken-token-tp7581415p7581421.html Sent from the Shiro User mailing list archive at Nabble.com.
