-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Delbecq wrote:
> Current strategy works (it's separated in 2 steps inside a common-chain
> of operation), but it makes wuite a few lines to try to detect user
> login, and if tomcat was already providing such event that could be
> handled
Current strategy works (it's separated in 2 steps inside a common-chain
of operation), but it makes wuite a few lines to try to detect user
login, and if tomcat was already providing such event that could be
handled by a context listener, that would have been, perhaps, cleaner.
En l'instant précis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Delbecq wrote:
> For now, the layout is Filter that check userPrincipal. If user
> principal is not null for the first time, issues that check, mark
> that user got checked for next times, in session, and continue query.
> However, if i
Hello,
I'm in a situation where i need some operations to be done upon user
login. The idea is, when a user access a secured area, it get's first
promped for http auth (security constraint, that part is working without
trouble), but when the user get authenticated, before giving user his
request r
