| Package Data | |
|---|---|
| Maintainer Username: | acoustep |
| Maintainer Contact: | acoustep+entrustgui@fastmail.co.uk (Mitch Stanley) |
| Package Create Date: | 2015-08-05 |
| Package Last Update: | 2022-04-07 |
| Language: | PHP |
| License: | MIT |
| Last Refreshed: | 2024-11-15 15:15:38 |
| Package Statistics | |
|---|---|
| Total Downloads: | 24,835 |
| Monthly Downloads: | 103 |
| Daily Downloads: | 1 |
| Total Stars: | 110 |
| Total Watchers: | 8 |
| Total Forks: | 22 |
| Total Open Issues: | 2 |
Entrust GUI is a Admin Interface that makes the administration of users, roles and permissions easier for the Entrust package.
This package is currently not for handling authentication, authorisation or registration of users.
For Laravel 5.2 and 5.3 see the 5.2 branch for installation details.
Add the package to your composer.json file
"acoustep/entrust-gui": "dev-master"
Add the service provider to your config/app.php file
Acoustep\EntrustGui\EntrustGuiServiceProvider::class,
Add the Entrust Alias to your config/app.php file as well.
'Entrust' => Zizaco\Entrust\EntrustFacade::class,
Publish the configuration file(s)
php artisan vendor:publish --tag="config"
If you haven't already set up Entrust then make the migration file and run the migration.
php artisan entrust:migration
php artisan migrate
Entrust GUI uses esensi/model which means you can set your validation rules in your models.
To generate User, Role and Permission models run the entrust-gui:models command.
php artisan entrust-gui:models
See the manually creating models section if you prefer to adjust your current model files.
By default, all three files are published into the app_path() directory. You can specify the files separately and the location
Add the Entrust GUI middleware to app\Http\Kernal.php. This middleware will allow users with the role admin (case sensitive) to access Entrust GUI and deny other users.
protected $routeMiddleware = [
// ...
'entrust-gui.admin' => \Acoustep\EntrustGui\Http\Middleware\AdminAuth::class,
];
At this point you're all good to go. See Getting Started for how to use the package.
By default all routes are prefixed with /entrust-gui.
/entrust-gui/users
/entrust-gui/roles
/entrust-gui/permissions
You can change this prefix by editing route-prefix in config/entrust-gui.php.
'route-prefix' => 'admin'
Pointing your app to /entrust-gui/users will redirect you to /auth/login if you are not logged in as admin using the default entrust-gui.admin middleware.
If you have not set up Laravel authentication you will see a NotFoundHttpException exception. See the Laravel Authentication documentation for setting up the Login system in Laravel 5.1.
By default Entrust GUI uses entrust-gui.admin for middleware. This allows logged in users with the admin role to access it.
You can change the middleware in config/entrust-gui.php in the middleware setting.
If you wish to test out the system without middleware then go to config/entrust-gui.php and set middleware to null.
'middleware' => null,
If you want to change the name of the role that has access to the admin middleware, update middleware-role in the configuration file.
"middleware-role" => 'sudo-admin',
To use your own layout override the layout key in config/entrust-gui.php with the template you wish to use.
"layout" => "app", // located in views/app.blade.php
Each template yields to heading and content so make sure your new layout has those sections.
<html>
<head>
<meta charset="UTF-8">
<title>title</title>
</head>
<body>
<h1>@yield('heading')</h1>
@include('entrust-gui::partials.notifications')
@yield('content')
</body>
</html>
To edit the template files you first need to publish them
php artisan vendor:publish --tag="views"
All files are then stored in the resources/views/vendor/entrust-gui directory.
You may wish to link to pages in your own templates. EntrustGUI follows Laravel's Route::resource method with the exception of show.
route('entrust-gui::users.index')
route('entrust-gui::users.create')
route('entrust-gui::users.destroy', $id)
route('entrust-gui::users.update', $id)
route('entrust-gui::users.edit', $id)
The following event classes are available:
UserCreatedEvent, UserDeletedEvent, UserUpdatedEvent.RoleCreatedEvent, RoleDeletedEvent, RoleUpdatedEvent.PermissionCreatedEvent, PermissionDeletedEvent, PermissionUpdatedEvent.<?php
namespace App\Listeners;
use Acoustep\EntrustGui\Events\UserCreatedEvent;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Log;
class UserCreatedListener
{
/**
* Create the event listener.
*
* @return void
*/
public function __construct()
{
//
}
/**
* Handle the event.
*
* @param UserCreatedEvent $event
* @return void
*/
public function handle(UserCreatedEvent $event)
{
Log::info('created: '.$event->user->email);
}
}
Add the listeners you need to use to app/Providers/EventServiceProvider.php.
protected $listen = [
'Acoustep\EntrustGui\Events\UserCreatedEvent' => [
'App\Listeners\UserCreatedListener',
],
'Acoustep\EntrustGui\Events\UserUpdatedEvent' => [
'App\Listeners\UserUpdatedListener',
],
'Acoustep\EntrustGui\Events\UserDeletedEvent' => [
'App\Listeners\UserDeletedListener',
],
'Acoustep\EntrustGui\Events\RoleCreatedEvent' => [
'App\Listeners\RoleCreatedListener',
],
'Acoustep\EntrustGui\Events\RoleUpdatedEvent' => [
'App\Listeners\RoleUpdatedListener',
],
'Acoustep\EntrustGui\Events\RoleDeletedEvent' => [
'App\Listeners\RoleDeletedListener',
],
'Acoustep\EntrustGui\Events\PermissionCreatedEvent' => [
'App\Listeners\PermissionCreatedListener',
],
'Acoustep\EntrustGui\Events\PermissionUpdatedEvent' => [
'App\Listeners\PermissionUpdatedListener',
],
'Acoustep\EntrustGui\Events\PermissionDeletedEvent' => [
'App\Listeners\PermissionDeletedListener',
]
];
Run the publish translation command
php artisan vendor:publish --tag="translations"
Translations are then published to resources/lang/vendor/entrust-gui.
Update your User model to the following:
<?php namespace App;
use Esensi\Model\Contracts\HashingModelInterface;
use Esensi\Model\Contracts\PurgingModelInterface;
use Esensi\Model\Contracts\ValidatingModelInterface;
use Esensi\Model\Traits\HashingModelTrait;
use Esensi\Model\Traits\PurgingModelTrait;
use Esensi\Model\Traits\ValidatingModelTrait;
use Illuminate\Auth\Authenticatable;
use Illuminate\Auth\Passwords\CanResetPassword;
use Illuminate\Contracts\Auth\Authenticatable as AuthenticatableContract;
use Illuminate\Contracts\Auth\CanResetPassword as CanResetPasswordContract;
use Illuminate\Database\Eloquent\Model;
use Zizaco\Entrust\Traits\EntrustUserTrait;
class User extends Model implements AuthenticatableContract, CanResetPasswordContract, ValidatingModelInterface, HashingModelInterface, PurgingModelInterface
{
use Authenticatable, CanResetPassword, ValidatingModelTrait, EntrustUserTrait, PurgingModelTrait, HashingModelTrait;
protected $throwValidationExceptions = true;
/**
* The database table used by the model.
*
* @var string
*/
protected $table = 'users';
/**
* The attributes that are mass assignable.
*
* @var array
*/
protected $fillable = ['name', 'email', 'password', 'password_confirmation'];
/**
* The attributes excluded from the model's JSON form.
*
* @var array
*/
protected $hidden = ['password', 'remember_token'];
protected $purgeable = [
'password_confirmation',
];
protected $hashable = ['password'];
protected $rulesets = [
'creating' => [
'email' => 'required|email|unique:users',
'password' => 'required|confirmed',
],
'updating' => [
'email' => 'required|email|unique:users',
'password' => 'confirmed',
],
];
}
Update config/entrust-gui.php
'confirmable' => true,
Generating a specific model
php artisan entrust-gui:models User
Changing the model directory destination
php artisan entrust-gui:models --path=new/path
Skipping confirmation prompts for overwriting existing files
php artisan entrust-gui:models --force
Here are User, Role and Permission models. Make sure these parameters are and traits are included for the package to work as intended.
<?php namespace App;
use Esensi\Model\Contracts\HashingModelInterface;
use Esensi\Model\Contracts\ValidatingModelInterface;
use Esensi\Model\Traits\HashingModelTrait;
use Esensi\Model\Traits\ValidatingModelTrait;
use Illuminate\Auth\Authenticatable;
use Illuminate\Auth\Passwords\CanResetPassword;
use Illuminate\Contracts\Auth\Authenticatable as AuthenticatableContract;
use Illuminate\Contracts\Auth\CanResetPassword as CanResetPasswordContract;
use Illuminate\Database\Eloquent\Model;
use Zizaco\Entrust\Traits\EntrustUserTrait;
class User extends Model implements AuthenticatableContract, CanResetPasswordContract, ValidatingModelInterface, HashingModelInterface
{
use Authenticatable, CanResetPassword, ValidatingModelTrait, EntrustUserTrait, HashingModelTrait;
protected $throwValidationExceptions = true;
/**
* The database table used by the model.
*
* @var string
*/
protected $table = 'users';
/**
* The attributes that are mass assignable.
*
* @var array
*/
protected $fillable = ['name', 'email', 'password'];
/**
* The attributes excluded from the model's JSON form.
*
* @var array
*/
protected $hidden = ['password', 'remember_token'];
protected $hashable = ['password'];
protected $rulesets = [
'creating' => [
'email' => 'required|email|unique:users',
'password' => 'required',
],
'updating' => [
'email' => 'required|email|unique:users',
'password' => '',
],
];
}
<?php namespace App;
use Esensi\Model\Contracts\ValidatingModelInterface;
use Esensi\Model\Traits\ValidatingModelTrait;
use Zizaco\Entrust\EntrustRole;
class Role extends EntrustRole implements ValidatingModelInterface
{
use ValidatingModelTrait;
protected $throwValidationExceptions = true;
protected $fillable = [
'name',
'display_name',
'description',
];
protected $rules = [
'name' => 'required|unique:roles',
'display_name' => 'required|unique:roles',
];
}
<?php namespace App;
use Esensi\Model\Contracts\ValidatingModelInterface;
use Esensi\Model\Traits\ValidatingModelTrait;
use Zizaco\Entrust\EntrustPermission;
class Permission extends EntrustPermission implements ValidatingModelInterface
{
use ValidatingModelTrait;
protected $throwValidationExceptions = true;
protected $fillable = [
'name',
'display_name',
'description',
];
protected $rules = [
'name' => 'required|unique:permissions',
];
}
Includes a new config key, "unauthorized-url" which lets you set the redirection if a user is not authorized. If this key is not found, it will use the old url, /auth/login. The default is set to /auth/login to match Laravel 5.1's documentation on the authentication routes.
Starting from 0.4.0 Entrust GUI switches from dwightwatson/validating to esensi/model.
Hashing passwords has moved from the package to the User model.
Update your User model to the one in the latest documentation.
Add 'confirmable' => false, to your configuration file.
If you intend to use the confirmable option and have already published the views add the following to your resources/views/vendor/entrust-gui/users/partials/form.blade.php template
@if(Config::get('entrust-gui.confirmable') === true)
<div class="form-group">
<label for="password">Confirm Password</label>
<input type="password" class="form-control" id="password_confirmation" placeholder="Confirm Password" name="password_confirmation">
</div>
@endif