Permission management for Ember applications.
@bagaar/ember-permissions is an addon that allows you to manage and validate permissions for the current session. It also allows you to define required permissions per route so you can protect specific parts of your application. Instead of using a mixin to protect your routes, the addon allows you to define the required permissions per route in a single file. Specific handlers can be added to determine what needs to happen when a transition occurs that is denied.
- Ember.js v4.8 or above
- Embroider or ember-auto-import v2
ember install @bagaar/ember-permissionsFirst, we need to let the permissions service know which permissions are available for the current session. In the example below, we're using an additional api service to request the permissions from an API. Afterwards, we pass along the permissions to the permissions service via the setPermissions method.
// app/routes/protected.js
import Route from '@ember/routing/route';
import { service } from '@ember/service';
export default class ProtectedRoute extends Route {
@service('api') apiService;
@service('permissions') permissionsService;
async beforeModel() {
const permissions = await this.apiService.request('/permissions');
this.permissionsService.setPermissions(permissions);
}
}Once the permissions are set, we can start checking their presence. In the example below, we use the has-permissions helper to conditionally render a delete button based on the presence of the delete-users permission.
NOTE: If you need to validate permissions inside a JavaScript file, you can use the
hasPermissionsor thehasSomePermissionsmethod on thepermissionsservice instead.
Start off with defining the required permissions per route. You're free to define them where you want, as long as the format is the same as shown below.
// app/route-permissions.js
export default {
'users.index': ['view-users'],
'users.create': ['create-users'],
'users.edit': ['edit-users'],
};Next, edit the protected route from step 1 as follows:
- Use the
setRoutePermissionsmethod to pass along the required permissions per route to thepermissionsservice - Add a route-access-denied handler to determine what needs to happen when a transition occurs that is denied
- Call
enableRouteValidationwith the initial transition
// app/routes/protected.js
import { registerDestructor } from '@ember/destroyable';
import Route from '@ember/routing/route';
import { service } from '@ember/service';
import ROUTE_PERMISSIONS from 'app-name/route-permissions';
export default class ProtectedRoute extends Route {
@service('api') apiService;
@service('permissions') permissionsService;
@service('router') routerService;
async beforeModel(transition) {
const permissions = await this.apiService.request('/permissions');
this.permissionsService.setPermissions(permissions);
this.permissionsService.setRoutePermissions(ROUTE_PERMISSIONS);
const handler = (/* deniedTransition */) => {
// Handle the denied transition.
// E.g. redirect to a generic error route:
this.routerService.replaceWith('error', { error: 'access-denied' });
};
this.permissionsService.addRouteAccessDeniedHandler(handler);
registerDestructor(this, () => {
this.permissionsService.removeRouteAccessDeniedHandler(handler);
});
this.permissionsService.enableRouteValidation(transition);
}
}Now, each transition will be validated (including the provided initial transition) against the required permissions per route. If a transition is denied, the added route-access-denied handler will be called with the denied transition.
Since the required permissions per route are now set, we can start checking if routes can be accessed. In the example below, we use the can-access-route helper to do so.
NOTE: If you need to validate if a route can be accessed inside a JavaScript file, you can use the
canAccessRoutemethod on thepermissionsservice instead.
Set the permissions for the current session.
An array of permissions.
/
permissionsService.setPermissions([
'view-users',
'create-users',
'edit-users',
]);Set the required permissions per route.
An object of which the keys are route names and the values are arrays of required permissions.
/
permissionsService.setRoutePermissions({
'users.index': ['view-users'],
'users.create': ['create-users'],
'users.edit': ['edit-users'],
});Check if all the provided permissions are available for the current session.
An array of permissions.
Returns true if all the provided permissions are available for the current session, false if otherwise.
permissionsService.hasPermissions([
'view-users',
'create-users',
'edit-users',
]);Check if some of the provided permissions are available for the current session.
An array of permissions.
Returns true if some of the provided permissions are available for the current session, false if otherwise.
permissionsService.hasSomePermissions([
'view-users',
'create-users',
'edit-users',
]);Check if the provided route can be accessed.
A route's name.
Returns true if the provided route can be accessed, false if otherwise.
permissionsService.canAccessRoute('users.index');Tell the permissions service that it should start validating each transition (including the provided initial transition) and confirm that it's allowed based on the required permissions per route. If a transition is denied, all added route-access-denied handlers will be called with the denied transtion.
The initial transition.
/
permissionsService.enableRouteValidation(transition);Add a route-access-denied handler.
A handler.
/
const handler = (/* deniedTransition */) => {
// Handle the denied transition.
// E.g. redirect to a generic error route:
this.routerService.replaceWith('error', { error: 'access-denied' });
};
this.permissionsService.addRouteAccessDeniedHandler(handler);Remove a previously added route-access-denied handler.
A handler.
/
const handler = (/* deniedTransition */) => {
// Handle the denied transition.
// E.g. redirect to a generic error route:
this.routerService.replaceWith('error', { error: 'access-denied' });
};
this.permissionsService.removeRouteAccessDeniedHandler(handler);Check if all the provided permissions are available for the current session.
Separate permissions.
Returns true if all the provided permissions are available for the current session, false if otherwise.
Check if some of the provided permissions are available for the current session.
Separate permissions.
Returns true if some of the provided permissions are available for the current session, false if otherwise.
Check if the provided route can be accessed.
A route's name.
Returns true if the provided route can be accessed, false if otherwise.
See the Contributing guide for details.
This project is licensed under the MIT License.