List of usage examples for org.springframework.context ApplicationEventPublisherAware interface-usage
From source file org.acegisecurity.providers.ProviderManager.java
/**
* Iterates an {@link Authentication} request through a list of {@link AuthenticationProvider}s.
*
* Can optionally be configured with a {@link ConcurrentSessionController} to limit the number of sessions a user can
* have.
* <p>
From source file org.acegisecurity.ui.AbstractProcessingFilter.java
/**
* Abstract processor of browser-based HTTP-based authentication requests.
* <p>
* This filter is responsible for processing authentication requests. If
* authentication is successful, the resulting {@link Authentication} object
* will be placed into the <code>SecurityContext</code>, which is guaranteed
From source file org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.java
/**
* Detects if there is no <code>Authentication</code> object in the <code>SecurityContext</code>, and populates it
* with a remember-me authentication token if a {@link org.acegisecurity.ui.rememberme.RememberMeServices}
* implementation so requests.<p>Concrete <code>RememberMeServices</code> implementations will have their {@link
* org.acegisecurity.ui.rememberme.RememberMeServices#autoLogin(HttpServletRequest, HttpServletResponse)} method
* called by this filter. The <code>Authentication</code> or <code>null</code> returned by that method will be placed
From source file org.acegisecurity.ui.switchuser.SwitchUserProcessingFilter.java
/**
* Switch User processing filter responsible for user context switching.<p>This filter is similar to Unix 'su'
* however for Acegi-managed web applications. A common use-case for this feature is the ability to allow
* higher-authority users (i.e. ROLE_ADMIN) to switch to a regular user (i.e. ROLE_USER).</p>
* <p>This filter assumes that the user performing the switch will be required to be logged in as normal (i.e.
* ROLE_ADMIN user). The user will then access a page/controller that enables the administrator to specify who they
From source file org.acegisecurity.ui.x509.X509ProcessingFilter.java
/**
* Processes the X.509 certificate submitted by a client browser when HTTPS is used with client-authentication
* enabled.<p>An {@link X509AuthenticationToken} is created with the certificate as the credentials.</p>
* <p>The configured authentication manager is expected to supply a provider which can handle this token (usually
* an instance of {@link org.acegisecurity.providers.x509.X509AuthenticationProvider}).</p>
* <p>If authentication is successful, an {@link
From source file org.alfresco.repo.admin.patch.AbstractPatch.java
/** * Base implementation of the patch. This class ensures that the patch is thread- and transaction-safe. * * @author Derek Hulley */ public abstract class AbstractPatch implements Patch, ApplicationEventPublisherAware {
From source file org.alfresco.repo.content.caching.CachingContentStore.java
/**
* Implementation of ContentStore that wraps any other ContentStore (the backing store)
* transparently providing caching of content in that backing store.
* <p>
* CachingContentStore should only be used to wrap content stores that are significantly
* slower that FileContentStore - otherwise performance may actually degrade from its use.
From source file org.alfresco.repo.content.caching.cleanup.CachedContentCleaner.java
/**
* Cleans up redundant cache files from the cached content file store. Once references to cache files are
* no longer in the in-memory cache, the binary content files can be removed.
*
* @author Matt Ward
*/
From source file org.alfresco.repo.security.sync.ChainingUserRegistrySynchronizer.java
/**
* A <code>ChainingUserRegistrySynchronizer</code> is responsible for synchronizing Alfresco's local user (person) and
* group (authority) information with the external subsystems in the authentication chain (most typically LDAP
* directories). When the {@link #synchronize(boolean, boolean)} method is called, it visits each {@link UserRegistry} bean in
* the 'chain' of application contexts, managed by a {@link ChildApplicationContextManager}, and compares its
* timestamped user and group information with the local users and groups last retrieved from the same source. Any
From source file org.alfresco.repo.security.sync.TenantChainingUserRegistrySynchronizer.java
/**
* A <code>TenantChainingUserRegistrySynchronizer</code> is responsible for
* synchronizing Alfresco's local user (person) and group (authority)
* information with the external subsystems in the authentication chain (most
* typically LDAP directories). When the {@link #synchronize(boolean)} method is
* called, it visits each {@link UserRegistry} bean in the 'chain' of