Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community ForumsAbstractChainableSecurityFilter
https://www.eclipse.org/forums/index.php/mv/msg/417257/960380/#msg_960380
doFilter(ServletRequest in, ServletResponse out, final FilterChain chain)
in AbstractChainableSecurityFilter is final? I would like to reuse existing functionality in my customized SecurityFilter.
If there is no specific reason, I would create a ticket to remove final from this method.]]>Adrian Moser2012-10-27T12:26:20-00:00Re: AbstractChainableSecurityFilter
https://www.eclipse.org/forums/index.php/mv/msg/417257/962867/#msg_962867
Yes, there is a reason. doFilter should not be overridden. The implementing class has to implement
where the logic is held. See org.eclipse.scout.http.servletfilter.security.LDAPSecurityFilter for an example.
If this doesn't help you please give an hint, what you want to customize in your SecurityFilter. Perhaps there is an other possibility how to do this.
Greetings Stephan]]>Stephan Leicht Vogt2012-10-29T11:43:36-00:00Re: AbstractChainableSecurityFilter
https://www.eclipse.org/forums/index.php/mv/msg/417257/963052/#msg_963052
Consider the following login scenario:
- login either by request parameters that contain username and encrypted password
(e.g. for embedding my application into an existing webapp)
- or by traditional login using basic authentication (login box)
where both login box and parameter login would authenticate against data stored in the same database.
Actually I do not see the reason why doFilter must be final.