-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 10/12/2009 11:03 AM, André Warnier wrote: > [servlet-filter mechanisms] consist of wrapping all your to-be-protected webapps in a servlet > filter, which authenticates each request before it even gets to your > webapp. Servlet filters are defined at the Servlet Spec level, so > are portable. To the webapp, it is transparent. It just finds an > authenticated user whenever it runs. The filter itself determines > what kind of authentication happens, using which back-end etc.. > Here are two examples : > http://securityfilter.sourceforge.net/ > http://www.ioplex.com Another one is ACEGI (or "Spring Security") which, I believe, includes SSO capabilities (which securityfilter does not): http://www.acegisecurity.org/ - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrTW7wACgkQ9CaO5/Lv0PCkMgCfdoxVvuoHVQd82NccfaXbOf7+ My8An3lElTBRv1z/fO7adtzSee47dcKs =8KJ8 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
