All Classes and Interfaces

Class
Description
 
 
 
Invalidate all user sessions after all passwords have been expired from a director.
 
 
Specialized filter to block OpenSocial requests specifically made by the Apache Shindig OpenSocial implementation.
 
This class has the responsibility of returning an instance of the 'Crowd' application (not constructing it).
 
Default implementation of ExpirableUserTokenService backed by a storage DAO.
Default implementation of InviteUserTokenService backed by a storage DAO.
 
 
This has a thread local that contains the current RequestContext.
Helper class to perform mailing tasks for forgotten login.
 
 
 
Servlet filter responsible for putting the current HTTP request and session in a thread local.
 
 
 
A specialized RuleBuilder for mail server rules
 
 
 
 
Text macros used by MailTemplateRenderer to dynamically generate values for emails sent by Crowd.
Simple renderer, which naive substitutes macros into supplied values.
A wrapper around the JavaMail Transport class that handles the creation/closing of the Session.
A marker interface for events that internal listeners may ignore.
A special noop event fired when the user requests their password to be reset.It is used instead of RequestResetPasswordEvent to avoid sending emails, e.g.
 
 
A job that sends email notifications about password expiry for users whose passwords will soon expire.
 
Listens to directory events that may affect the authentication credentials or the ability to reset a password and invalidates the password reset tokens for affected users.
Manages plugin properties.
 
Removes internal permissions from group so that it can be deleted without violating any foreign key constraints.
This takes care of invalidating a user's session after their password is changed.
 
Contains info about the currently executing HttpServletRequest and HttpServletResponse.
Handles raciness of TokenAuthenticationManagerImpl by retrying authentications that fail due to a concurrent authentication creating a token.
 
 
Responsible for the creation of Token's this should be the only way you create a Token for Crowd
The TokenGenerator is responsible for generating tokens when a successful authentication has occurred.
Handles the creation of a 'random' token key
 
A marker interface for a SessionTokenStorage that should be used for token management.
{link Executor} wrapper, that wraps executed code into a transaction.
 
Handles the list of proxy servers whose X-Forwarded-For headers we trust.
Responsible for creating and sending email notifications to users created in Crowd
Manager class responsible for email notifications sent to new users created in Crowd.
Deletes the appropriate Tokens when a User or Directory is deleted, or when a user is renamed.
All methods on this class require at least ADMIN permissions.