FR wrote:
The standard workaround mentioned is to place user information in
session, but that won't work across webapps using Single Sign On. I
have a bunch of webapps, only one of which is protected and requires
login, the rest work fine without logging in, but display different
information whe
I recently attempted to upgrade our sites from tomcat 5.5.17, and at
some point the behavior of request.getUserPrincipal() changed so it
now returns null for all URLs except those declared to require
authentication. (Actually, it seems like the behavior was changed
long before 5.5.17, but regresse
