| java.lang.Object org.acegisecurity.providers.anonymous.AnonymousProcessingFilter
AnonymousProcessingFilter | public class AnonymousProcessingFilter implements Filter,InitializingBean(Code) | | Detects if there is no Authentication object in the SecurityContextHolder , and
populates it with one if needed.Do not use this class directly. Instead configure web.xml
to use the
org.acegisecurity.util.FilterToBeanProxy .
author: Ben Alex version: $Id: AnonymousProcessingFilter.java 1496 2006-05-23 13:38:33Z benalex $ |
applyAnonymousForThisRequest | protected boolean applyAnonymousForThisRequest(ServletRequest request)(Code) | | Enables subclasses to determine whether or not an anonymous authentication token should be setup for
this request. This is useful if anonymous authentication should be allowed only for specific IP subnet ranges
etc.
Parameters: request - to assist the method determine request details true if the anonymous token should be setup for this request (provided that the requestdoesn't already have some other Authentication inside it), or false if noanonymous token should be setup for this request |
destroy | public void destroy()(Code) | | Does nothing - we reply on IoC lifecycle services instead.
|
isRemoveAfterRequest | public boolean isRemoveAfterRequest()(Code) | | |
setRemoveAfterRequest | public void setRemoveAfterRequest(boolean removeAfterRequest)(Code) | | Controls whether the filter will remove the Anonymous token after the request is complete. Generally
this is desired to avoid the expense of a session being created by
org.acegisecurity.context.HttpSessionContextIntegrationFilter HttpSessionContextIntegrationFilter simply to
store the Anonymous authentication token. Defaults to true , being the most optimal and
appropriate option (ie AnonymousProcessingFilter will clear the token at the end of each request,
thus avoiding the session creation overhead in a typical configuration.
Parameters: removeAfterRequest - DOCUMENT ME! |
|
|