Re: WAFFLE logging with Tomcat

1,755 views
Skip to first unread message

Daniel Doubrovkine

unread,
Apr 25, 2014, 7:09:44 AM4/25/14
to waffle...@googlegroups.com
You're using a Tomcat valve, not the security filter. Start with

waffle.apache.NegotiateAuthenticator.level = INFO

I also suspect that the global logging.properties may not be the right place for this, but I am not sure. Waffle now uses logback, which is configured through logback.xml, I don't know how these things fit together with tomcat valves.

It would be nice to update documentation on this once you have figured it out.



On Tue, Apr 22, 2014 at 10:08 AM, Glen Ditchfield <glen.di...@investorsgroup.com> wrote:
I have set up a Tomcat server to use WAFFLE. The authentication is working (and is just amazingly easy!) but I haven't figured out how to adjust the logging levels.

I used http://code.dblock.org/single-sign-on-tomcat-negotiate-authenticator-kerberos-ntlm-w-waffle and https://github.com/dblock/waffle/blob/master/Docs/ServletSingleSignOnSecurityFilter.md as my guides. What I did was
  • Installed Tomcat 7.0.53 on Windows Server 2003 x64, as a service using the 32-bit/64-bit service installer apache-tomcat-7.0.53.exe. The configuration GUI program says that Tomcat started with Java options
    -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
    -Djava.util.logging.config.file=D:\Tomcat\apache-tomcat-7.0.53\conf\logging.properties
    and that "Redirect Stdout" and "Redirect StdError" are set to"auto".
  • Downloaded WAFFLE1.5, and copied guava-13.0.1.jar, jna-3.5.0.jar, logback-classic-1.0.7.jar, logback-core-1.0.7.jar, platform-3.5.0.jar, slf4j-1.7.2.jar, waffle-jna.jar, and waffle-tomcat7.jar to the Tomcat lib directory.
  • Added
    <Valve className="waffle.apache.NegotiateAuthenticator" />
    <Realm className="waffle.apache.WindowsRealm" />
    to the Tomcat Manager's context.xml.
  • Added security-role and security-constraint elements to the Manager's web.xml.
  • Added
    waffle.servlet.NegotiateSecurityFilter.level = INFO
    waffle.servlet.spi.SecurityFilterProviderCollection.level = INFO
    waffle.servlet.spi.NegotiateSecurityFilterProvider.level = INFO
    waffle.servlet.spi.BasicSecurityFilterProvider.level = INFO

    to Tomcat's conf\logging.properties.

Given that set-up, WAFFLE log messages at the DEBUG level appear in the *-stdout.*.log files. No WAFFLE messages appear in any other log. I'd like to cut that back to just the INFO messages, but if I understand log4j.properties (admittedly a doubtful proposition) that's what the four lines above are supposed to do.

Can someone here tell me what I missed?

--
You received this message because you are subscribed to the Google Groups "waffle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to waffle-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

dB. | Moscow - Geneva - Seattle - New York
code.dblock.org - @dblockdotorg - artsy.net - github/dblock

Reply all
Reply to author
Forward
0 new messages