You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/12/04 11:31:18 UTC

DO NOT REPLY [Bug 25194] New: - Filters are not matched to j_security_check

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25194>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25194

Filters are not matched to j_security_check

           Summary: Filters are not matched to j_security_check
           Product: Tomcat 4
           Version: 4.1.29
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: thomas2.maesing@bgs-ag.de


Dear all,

the servlet spec 2.3 doesn't provide a direct hook for a user is authenticated 
event. The only possible way (which is also proposed by some postings in the 
web) seems to be to map a filter to the "Resource" j_security_check and do the 
necessary things when the filterchain.doFilter() method returns and before the 
server sends the redirect to the original Resource to the client. We have tried 
this way with a form based login but the filter isn't called.

Best regards

Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org