Download the PHP package genealabs/laravel-governor without Composer

Governor For Laravel

Manage authorization with granular role-based permissions in your Laravel apps.

Goal

Provide a simple method of managing ACL in a Laravel application built on the Laravel Authorization functionality. By leveraging Laravel's native Authorization functionality there is no additional learning or implementation curve. All you need to know is Laravel, and you will know how to use Governor for Laravel.

Requirements

• PHP >=7.1.3
• Laravel >= 5.5
• Bootstrap 3 (needs to be included in your layout file)
• FontAwesome 4 (needs to be included in your layout file)

Installation

The user with the lowest primary key will be set up as the SuperAdmin. If you're starting on a new project, be sure to add an initial user now. If you already have users, you can update the role-user entry to point to your intended user, if the first user is not the intended SuperAdmin. Now let's get the package installed.

Install via composer:

Implementation

1. First we need to update the database by running the migrations and data seeders:

2. If you have seeders of your own, run them now:

3. Next, assign permissions (this requires you have users already populated):

4. Now we need to make the assets available:

5. Lastly, add the Governable trait to the User model of your app:

Upgrading

The following upgrade guides should help navigate updates with breaking changes.

From 0.11.5+ to 0.12 [Breaking]

The role_user pivot table has replaced the composite key with a primary key, as Laravel does not fully support composite keys. Run:

From 0.11 to 0.11.5 [Breaking]

The primary keys of the package's tables have been renamed. (This should have been a minor version change, instead of a patch, as this was a breaking change.) Run:

From 0.10 to 0.11 [Breaking]

The following traits have changed:

• Governable has been renamed to Governing.
• Governed has been renamed to Governable.

• the governor_created_by has been renamed to governor_owned_by. Run migrations to update your tables.

• replace any reference in your app from governor_created_by to governor_owned_by.

From 0.6 to Version 0.10 [Breaking]

To upgrade from version previous to 0.10.0, first run the migrations and seeders, then run the update seeder:

to 0.6 [Breaking]

1. If you were extending GeneaLabs\LaravelGovernor\Policies\LaravelGovernorPolicy, change to extend GeneaLabs\LaravelGovernor\Policies\BasePolicy;
2. Support for version of Laravel lower than 5.5 has been dropped.

Configuration

If you need to make any changes (see Example selection below for the default config file) to the default configuration, publish the configuration file:

and make any necessary changes. (We don't recommend publishing the config file if you don't need to make any changes.)

Views

If you would like to customize the views, publish them:

and edit them in resources\views\vendor\genealabs\laravel-governor.

Policies

Policies are now auto-detected and automatically added to the entities list. You will no longer need to manage Entities manually. New policies will be available for role assignment when editing roles. Check out the example policy in the Examples section below. See Laravel's documentation on how to create policies and check for them in code: https://laravel.com/docs/5.4/authorization#writing-policies

Your policies must extend LaravelGovernorPolicy in order to function with Governor. By default you do not need to include any of the methods, as they are implemented automatically and perform checks based on reflection. However, if you need to customize anything, you are free to override any of the before, create, edit, view, inspect, and remove methods.

Checking Authorization

To validate a user against a given policy, use one of the keywords that Governor validates against: before, create, edit, view, inspect, and remove. For example, if the desired policy to check has a class name of BlogPostPolicy, you would authorize your user with something like $user->can('create', (new BlogPost)) or $user->can('edit', $blogPost).

Filter Queries To Show Ownly Allowed Items

Often it is desirable to let the user see only the items that they have access to. This was previously difficult and tedious. Using Nova as an example, you can now limit the index view as follows:

The available query filters are:
- `filterDeletable(Builder $query)`
- `filterUpdatable(Builder $query)`
- `filterViewable(Builder $query)`
- `filterViewAnyable(Builder $query)`

The same functionality is availabe via model scopes, as well:
- `deletable()`
- `updatable()`
- `viewable()`
- `viewAnyable()`

Tables

Tables will automatically be updated with a governor_owned_by column that references the user that created the entry. There is no more need to run separate migrations or work around packages that have models without a created_by property.

Admin Views

The easiest way to integrate Governor for Laravel into your app is to add the menu items to the relevant section of your app's menu (make sure to restrict access appropriately using the Laravel Authorization methods). The following routes can be added:

• Role Management: genealabs.laravel-governor.roles.index
• User-Role Assignments: genealabs.laravel-governor.assignments.index

For example:

403 Unauthorized

We recommend making a custom 403 error page to let the user know they don't have access. Otherwise the user will just see the default error message. See https://laravel.com/docs/5.4/errors#custom-http-error-pages for more details on how to set those up.

Authorization API

You can check a user's ability to perform certain actions via a public API. It is recommended to use Laravel Passport to maintain session state between your client and your backend. Here's an example that checks if the currently logged in user can create GeneaLabs\LaravelGovernor\Role model records:

This next example checks if the user can edit GeneaLabs\LaravelGovernor\Role model records:

The abilities inspect, edit, and remove, except create and view, require the primary key to be passed.

Role-Check API

// TODO: add documentation

Examples

Config File

Policy

No Methods Required For Default Policies

Adding policies is crazily simple! All the work has been refactored out so all you need to worry about now is creating a policy class, and that's it!

Default Methods In A Policy Class

Adding any of the before, create, update, view, viewAny, delete, restore, and forceDelete methods to your policy is only required if you want to customize a given method.