- ⌂ io_comand_login
- Classes
- Content Types
Login Policy
A Login Policy defines the features and settings for a specific implementation of the Login Framework.
Fields
The Login Policy content type has the following fields.
- Identifier - Name used to identify the Login Policy from code, including the login::Constructor.
- Title - Human-friendly name.
- Description - Short description of the policy and how it can be used.
- General Settings
- System Title - Name of the system, website or app this login policy is used for.
- Administrator Title - Name of the system, website or app administrator or team.
- Administrator Email - Email address to contact for login issues and help.
- Administrator Phone - Phone number to contact for login issues and help.
- Administrator Hours - Hours of operation when the administrator will respond.
- Controllers - Identifies the features available for this login implementation.
- Login - Login Controller to use to handle the login process. For example, to validate a username and password.
- Change - Change Controller to use to handle login credential changes. For example, change password.
- Reset - Reset Controller to use to handle a request to reset login credentials. For example, reset password process.
- Unlock - Unlock Controller to use to unlock a locked user account.
- Models - Identifies the models available that supply information to the login controllers.
- Credentials - Credentials Model to set login credential requirements. For example, required password strength, days before reset required, etc.
- User - User Model to get and set user information. For example, get the user by ID, Username and Email.
- Log - Determines how login-related activity is logged and cleared. The default Log Model logs activity to the Login Security Log.
- Session - The model for managing a persistent user session. This enables a user to remain logged in persistently across interactions with the system. This does not require the use of PHP sessions. The default Session Model is the Cookie Session Model.
- Security Question - The security question model for this login implementation. This supports serving a random question for a user, challenging it, and managing them in the repository.
- Reset Code - The reset code model for this login implementation. This provides support for generating and challenging one-time codes for users who are resetting their credentials.
- Impersonation - The impersonation model for this login implementation. This provides support for logging in as other users to perform actions or test access.
- Notifications - Identifies the notifications available for this login implementation.
- System Lock Email - The email to send when the user is locked out of the system. If no email template is specified, no email will be sent.