- Identity interfaces
- User model example
- Diceware aka password generator
- Usage scenarios
- Configuration for Twitter Bootstrap
Usr module is inspired by the popular Yii-user module but written from scratch. It provides basic user actions like:
- logging in and out,
- password recovery and reset if expired
- registration with optional email verification,
- viewing and updating a minimal user profile along with changing password, profile pictures are supported
- user managment
It's goal is to be easier to integrate into current projects by not requiring to modify existing user database table and model. Only the UserIdentity class is used to provide all business logic by implementing few provided interfaces.
Key differences from yii-user:
- clean codebase, easier to read/review
- use good password hashing
- no need to modify current tables and models
- bundled mailer class
- built-in Hybridauth for logging using social site identities
- built-in Google Authenticator for two step authentication using one time passwords
Github repo: https://github.com/nineinchnick/yii-usr
Composer package: nineinchnick/yii-usr
[bash] curl -sS https://getcomposer.org/installer | php ./composer.phar require nineinchnick/yii-usr:dev-master
Download and unpack in protected/modules.
Enable the module in the config/main.php file:
return array( ...... 'modules'=>array( 'usr'=>array( 'userIdentityClass' => 'UserIdentity', ), ), )
See UsrModule.php file for full options reference.
To be able to use user managment, create auth items using the
createAuthItems command and assign them to a role or users.
Fast setup and/or new projects ¶
This assumes there are no user tables in the database and all features can be enabled.
- Copy migrations files from the module to your project and adjust their filenames and class names. Apply them.
- Copy the ExampleUserIdentity to your components directory changing it's name to UserIdentity, remove the abstract keyword from the class definition.
- Copy each file starting with Example from the models directory to your projects and remove that prefix. Remove the abstract keyword from the class definition.
Custom setup and/or existing projects ¶
If the module will be used with existing database tables and/or not all features will be used the identity class should be copied and adjusted or reimplemented from scratch.
Requirements for the UserIdentity class are described in next chapter.
Identity interfaces ¶
To be able to use all features of the Usr module, the UserIdentity class must implement some or all of the following interfaces.
For details, please read comments in each identity file or see the provided ExampleUserIdentity file.
This interface allows to create new identities (register) and update existing ones.
Active/disabled and email verification ¶
This interface allows:
- finding existing identities using one of its attributes.
- generating and verifying an activation key used to verify email and send a recovery link
Remember to invalidate the email if it changes in the save() method from the Editable interface.
Password history ¶
This interface allows password reset with optional tracking of used passwords. This allows to detect expired passwords and avoid reusing old passwords by users.
This interface allows finding local identity associated with a remote one (from an external social site) and creating such associations.
One Time Password ¶
This interface allow saving and retrieving a secret used to generate one time passwords. Also, last used password and counter used to generate last password are saved and retrieve to protect against reply attacks.
Profile Pictures ¶
Allows users to upload a profile picture. The example identity uses Gravatar to provide a default picture.
Allows to manage users:
- update their profiles (and pictures)
- change passwords
- assign authorization roles
- activate/disable and mark email as verified
- see details as timestamps of account creation, last profile update and last visit
User model example ¶
A sample ExampleUserIdentity and corresponding ExampleUser and ExampleUserUsedPassword models along with database migrations are provided respectively in the 'components', 'models' and 'migrations' folders.
They could be used as-is by extending from or copying to be modified to better suit a project.
To use the provided migrations it's best to copy them to your migrations directory and adjust the filenames and classnames to current date and time. Also, they could be modified to remove not needed features.
Diceware aka password generator ¶
A simple implementation of a Diceware Passphrase generator is provided to aid users when they need to create a good, long but also easy to remember passphrase.
Read more at the Diceware Passphrase homepage.
Custom profile fields ¶
It is possible to add more profile fields:
- Override view files in a theme.
- Create a behavior class extending FormModelBehavior.
- Add that behvaior in the UsrModule::profileFormBehaviors property.
- Remember to update setAttributes and getAttributes methods of your UserIdentity class to include new profile fields.
The behavior will include properties, rules and labels. Rules can contain inline validators defined in that behavior, just call them using the behaviorValidator helper method:
// BEHAVIOR_NAME is the key used in UsrModule::profileFormBehaviors // INLINE_VALIDATOR is the name of the inline validator method defined in the behavior array('attribute', 'behaviorValidator', 'behavior'=>'BEHAVIOR_NAME', 'validator'=>'INLINE_VALIDATOR', /* other params */),
Email templates ¶
Set the setPathViews and setPathLayouts keys under the mailerConfig module option.
Feel free to send new and updated translations to the author.
Usage scenarios ¶
Varios scenarios can be created by enabling or disabling following features:
- email verification
- account activation
Implementing those scenarios require some logic outside the scope of this module.
Public site ¶
Users can register by themselves. Their accounts are activated instantly or after verifying email.
Moderated site ¶
Users can register, but to allow them to log in an administrator must activate their accounts manually, optionally assigning an authorization profile. Email verification is optional and activation could trigger an email notification.
Configuration for Twitter Bootstrap ¶
If using the bootstrap extension, the following configuration may be used:
'usr' => array( 'layout' => '//layouts/centered', 'formClass'=>'bootstrap.widgets.TbActiveForm', 'detailViewClass'=>'bootstrap.widgets.TbDetailView', 'formCssClass'=>'form well', 'alertCssClassPrefix'=>'alert alert-', 'submitButtonCssClass'=>'btn btn-primary', 'htmlCss' => array( 'errorSummaryCss' => 'alert alert-error', 'errorMessageCss' => 'text-error', ), // mail ...mail config... ),
Besides that, all views could be overriden in a theme. A following skin can be used for user managment grid:
return array( 'default' => array( 'itemsCssClass' => 'table table-striped table-bordered table-condensed', 'pagerCssClass' => 'paging_bootstrap pagination', ), );
MIT or BSD