This is a callback interface which must be implemented by the class which does something after login attempt.
The interface for all classes which need to manage permissions.
SecurityCredentials contains security related attributes needed to uniquely identify user.
The secondary information needed by the security subsystem to identify user, such as: first name, lst name, email, etc.
This class checks role-based permissions associated with the given security context.
The wrapper interface for the Permission and possible actions, associated with the Permission.
The base class for all type of permissions.
The default implementation of the SecurityCredentials.
The default implementation of the SecurityPrincipals.
The default implementation of the SecurityProvider.
The SecurityManager is always active and must be initialized.
The security subsystem provides an access to data or resources based on credentials supplied by the user.
This class contains information needed by the security subsystem to uniquely identify user.
The singleton class which contains all security-checking related functions.
The login service must return an instance of the SecurityModel class.
The permission which is stored in the permanent storage (xml, database) as a pattern and retrieved by the security subsystem to compare with the list of permissions associated with the user.
Copyright © 2010-2017 Toolsverse. All Rights Reserved.