simplabs/ember-simple-auth

Name: ember-simple-auth

Owner: simplabs

Description: A library for implementing authentication/authorization in Ember.js applications.

Created: 2013-09-03 18:03:26.0

Updated: 2018-01-19 14:31:41.0

Pushed: 2018-01-19 21:47:16.0

Homepage: http://ember-simple-auth.com

Size: 8609

Language: JavaScript

GitHub Committers

UserMost Recent Commit# Commits

Other Committers

UserEmailMost Recent Commit# Commits

README

Build Status

Ember Simple Auth API docs

Slack Status

Ember Simple Auth supports all Ember.js versions starting with 1.12.

Ember Simple Auth

Logo

Ember Simple Auth is a lightweight library for implementing authentication/ authorization with Ember.js applications. It has minimal requirements with respect to application structure, routes etc. With its pluggable strategies it can support all kinds of authentication and authorization mechanisms.

Table of Contents

Basic Information

Usage

Core Feature Guides

Other Guides

Other Resources

What does it do?
How does it work?

Ember Simple Auth consists of 4 main building blocks - the session, a session store, authenticators and (optionally) authorizers.

The session service is the main interface to the library. It provides methods for authenticating and invalidating the session as well as for setting and reading session data.

The session store persists the session state so that it survives a page reload. It also synchronizes the session state across multiple tabs or windows of the application so that e.g. a logout in one tab or window also results in a logout in all other tabs or windows of the application.

Authenticators authenticate the session. An application can leverage multiple authenticators to support multiple ways of authentication such as sending credentials to the application's own backend server, Facebook, github etc.

Authorizers use the data retrieved by an authenticator and stored in the session to generate authorization data that can be injected into outgoing requests such as Ember Data requests.

Example App

Ember Simple Auth comes with a dummy app that implements a complete auth solution including authentication against the application's own server as well as Facebook, authorization of Ember Data requests and error handling. Check out that dummy app for reference. To start it, run

clone https://github.com/simplabs/ember-simple-auth.git
mber-simple-auth
 install && ember serve

and go to http://localhost:4200.

Installation

Installing the library is as easy as:

r install ember-simple-auth
Upgrading from ember-cli-simple-auth / pre-1.0 release?

The 1.0 release of ember-simple-auth introduced a lot of breaking changes, but thankfully the upgrade path isn't too hard.

Walkthrough

Once the library is installed, the session service can be injected wherever needed in the application. In order to display login/logout buttons depending on the current session state, inject the service into the respective controller or component and query its isAuthenticated property in the template:

pp/controllers/application.js
rt Ember from 'ember';

rt default Ember.Controller.extend({
ssion: Ember.inject.service('session')




andlebars
- app/templates/application.hbs --}}
 class="menu">

#if session.isAuthenticated}}
<a {{action 'invalidateSession'}}>Logout</a>
else}}
{{#link-to 'login'}}Login{{/link-to}}
/if}}
v>
 class="main">
outlet}}
v>

In the invalidateSession action call the session service's invalidate method to invalidate the session and log the user out:

pp/controllers/application.js
rt Ember from 'ember';

rt default Ember.Controller.extend({
ssion: Ember.inject.service('session'),



tions: {
invalidateSession() {
  this.get('session').invalidate();
}

For authenticating the session, the session service provides the authenticate method that takes the name of the authenticator to use as well as other arguments depending on specific authenticator used. To define an authenticator, add a new file in app/authenticators and extend one of the authenticators the library comes with, e.g.:

pp/authenticators/oauth2.js
rt OAuth2PasswordGrant from 'ember-simple-auth/authenticators/oauth2-password-grant';

rt default OAuth2PasswordGrant.extend();

With that authenticator and a login form like

- app/templates/login.hbs --}}
m {{action 'authenticate' on='submit'}}>
abel for="identification">Login</label>
input id='identification' placeholder='Enter Login' value=identification}}
abel for="password">Password</label>
input id='password' placeholder='Enter Password' type='password' value=password}}
utton type="submit">Login</button>
#if errorMessage}}
<p>{{errorMessage}}</p>
/if}}
rm>

the session can be authenticated with the session service's authenticate method:

pp/controllers/login.js
rt Ember from 'ember';

rt default Ember.Controller.extend({
ssion: Ember.inject.service('session'),

tions: {
authenticate() {
  let { identification, password } = this.getProperties('identification', 'password');
  this.get('session').authenticate('authenticator:oauth2', identification, password).catch((reason) => {
    this.set('errorMessage', reason.error || reason);
  });
}

The session service also provides the authenticationSucceeded and invalidationSucceeded events that are triggered whenever the session is successfully authenticated or invalidated (which not only happens when the user submits the login form or clicks the logout button but also when the session is authenticated or invalidated in another tab or window of the application). To have these events handled automatically, simply mix ApplicationRouteMixin into the application route:

pp/routes/application.js
rt Ember from 'ember';
rt ApplicationRouteMixin from 'ember-simple-auth/mixins/application-route-mixin';

rt default Ember.Route.extend(ApplicationRouteMixin);

The ApplicationRouteMixin automatically maps the session events to the sessionAuthenticated and sessionInvalidated methods it implements. The sessionAuthenticated method will transition to a configurable route while the sessionInvalidated method will reload the page to clear all potentially sensitive data from memory.

To make a route in the application accessible only when the session is authenticated, mix the AuthenticatedRouteMixin into the respective route:

pp/routes/protected.js
rt Ember from 'ember';
rt AuthenticatedRouteMixin from 'ember-simple-auth/mixins/authenticated-route-mixin';

rt default Ember.Route.extend(AuthenticatedRouteMixin);

This will make the route (and all of its subroutes) transition to the login route if the session is not authenticated. Add the login route in the router like this:

pp/router.js
er.map(function() {
is.route('login');

The route to transition to if the session is not authenticated can also be overridden to be another one than login.

It is recommended to nest all of an application's routes that require the session to be authenticated under a common parent route:

pp/router.js
er.map(function() {
is.route('login');
is.route('authenticated', { path: '' }, function() {
// all routes that require the session to be authenticated
;

To prevent a route from being accessed when the session is authenticated (which makes sense for login and registration routes for example), mix the UnauthenticatedRouteMixin into the respective route.

In order to add authorization information to outgoing API requests the application can define an authorizer. To do so, add a new file to app/authorizers, e.g.:

pp/authorizers/oauth2.js
rt OAuth2Bearer from 'ember-simple-auth/authorizers/oauth2-bearer';

rt default OAuth2Bearer.extend();

and use that to authorize a block of code via the session service's authorize method, e.g.:

.get('session').authorize('authorizer:oauth2', (headerName, headerValue) => {
nst headers = {};
aders[headerName] = headerValue;
ber.$.ajax('/secret-data', { headers });

To include authorization info in all Ember Data requests if the session is authenticated, mix the DataAdapterMixin into the application adapter:

pp/adapters/application.js
rt DS from 'ember-data';
rt DataAdapterMixin from 'ember-simple-auth/mixins/data-adapter-mixin';

rt default DS.JSONAPIAdapter.extend(DataAdapterMixin, {
thorizer: 'authorizer:oauth2'
The Session Service

The session service is the main interface to the library. It defines the authenticate, invalidate and authorize methods as well as the session events as shown above.

It also provides the isAuthenticated as well as the data properties. The latter can be used to get and set the session data. While the special authenticated section in the session data contains the data that was acquired by the authenticator when it authenticated the session and is read-only, all other session data can be written and will also remain in the session after it is invalidated. It can be used to store all kinds of client side data that needs to be persisted and synchronized across tabs and windows, e.g.:

.get('session').set('data.locale', 'de');
Authenticators

Authenticators implement the concrete steps necessary to authenticate the session. An application can leverage several authenticators for different kinds of authentication mechanisms (e.g. the application's own backend server, external authentication providers like Facebook etc.) while the session is only ever authenticated with one authenticator at a time. The authenticator to use is chosen when authentication is triggered via the name it is registered with in the Ember container:

.get('session').authenticate('authenticator:some');

Ember Simple Auth comes with 3 authenticators:

To use any of these authenticators in an application, define a new authenticator in app/authenticators, extend if from the Ember Simple Auth authenticator

pp/authenticators/oauth2.js
rt OAuth2PasswordGrantAuthenticator from 'ember-simple-auth/authenticators/oauth2-password-grant';

rt default OAuth2PasswordGrantAuthenticator.extend();

and invoke the session service's authenticate method with the respective name, specifying more arguments as needed by the authenticator:

.get('session').authenticate('authenticator:some', data);
Customizing an Authenticator

Authenticators are easily customized by setting the respective properties, e.g.:

pp/authenticators/oauth2.js
rt OAuth2PasswordGrantAuthenticator from 'ember-simple-auth/authenticators/oauth2-password-grant';

rt default OAuth2PasswordGrantAuthenticator.extend({
rverTokenEndpoint: '/custom/endpoint'
Implementing a custom Authenticator

Besides extending one of the predefined authenticators, an application can also implement fully custom authenticators. In order to do that, extend the abstract base authenticator that Ember Simple Auth comes with and override the authenticate, restore and (optionally) invalidate methods:

pp/authenticators/custom.js
rt Base from 'ember-simple-auth/authenticators/base';

rt default Base.extend({
store(data) {
?

thenticate(options) {
?

validate(data) {
?
Authorizers

Authorizers use the session data acquired by the authenticator to construct authorization data that can be injected into outgoing network requests. As the authorizer depends on the data that the authenticator acquires, authorizers and authenticators have to fit together.

Ember Simple Auth comes with 2 authorizers:

To use any of these authorizers in an application, define a new authorizer in app/authorizers, extend if from the Ember Simple Auth authorizer

pp/authorizers/oauth2.js
rt OAuth2Bearer from 'ember-simple-auth/authorizers/oauth2-bearer';

rt default OAuth2Bearer.extend();

and invoke the session service's authorize method with the respective name:

.get('session').authorize('authorizer:some', (/*authorization data*/) => {
 Use authorization data

Unlike in previous versions of Ember Simple Auth, authorization will not happen automatically for all requests the application issues anymore but has to be initiated explicitly via the service.

When using Ember Data you can mix the DataAdapterMixin in the application adapter to automatically authorize all API requests:

pp/adapters/application.js
rt DS from 'ember-data';
rt DataAdapterMixin from 'ember-simple-auth/mixins/data-adapter-mixin';

rt default DS.JSONAPIAdapter.extend(DataAdapterMixin, {
thorizer: 'authorizer:some'
Customizing an Authorizer

Authorizers are easily customized by setting the respective properties, e.g.:

pp/authorizers/devise.js
rt DeviseAuthorizer from 'ember-simple-auth/authorizers/devise';

rt default DeviseAuthorizer.extend({
entificationAttributeName: 'login'
Implementing a custom Authorizer

Besides extending one of the predefined authorizers, an application can also implement fully custom authorizers. In order to do that, extend the abstract base authorizer that Ember Simple Auth comes with and override the authorize method:

pp/authorizers/custom.js
rt Base from 'ember-simple-auth/authorizers/base';

rt default Base.extend({
thorize(sessionData, block) {
?
Session Stores

Ember Simple Auth persists the session state via a session store so it survives page reloads. There is only one store per application that can be defined in app/session-stores/application.js:

pp/session-stores/application.js
rt Cookie from 'ember-simple-auth/session-stores/cookie';

rt default Cookie.extend();

If the application does not define a session store, the adaptive store which uses localStorage if that is available or a cookie if it is not, will be used by default. To customize the adaptive store, define a custom store in app/session-stores/application.js that extends it and overrides the properties to customize.

Store Types

Ember Simple Auth comes with 4 stores:

Adaptive Store

The adaptive store stores its data in the browser's localStorage if that is available or in a cookie if it is not; this is the default store.

localStorage Store

The localStorage store stores its data in the browser's localStorage. This is used by the adaptive store if localStorage is available.

Cookie Store

The Cookie store stores its data in a cookie. This is used by the adaptive store if localStorage is not available. This store must be used when the application uses FastBoot.

sessionStorage Store

The sessionStorage store stores its data in the browser's sessionStorage. See the Web Storage docs for details on sessionStorage and localStorage. caniuse has up-to-date information on browser support of sessionStorage and localStorage.

Ephemeral Store

The ephemeral store stores its data in memory and thus is not actually persistent. This store is mainly useful for testing. Also the ephemeral store cannot keep multiple tabs or windows in sync as tabs/windows cannot share memory.

Customizing the Store

The session store is easily customized by setting the respective properties, e.g.:

pp/session-stores/application.js
rt AdaptiveStore from 'ember-simple-auth/session-stores/adaptive';

rt default AdaptiveStore.extend({
okieName: 'my-apps-session-cookie'
Implementing a custom Store

Besides using one of the predefined session stores, an application can also implement fully custom stores. In order to do that, extend the abstract base session store that Ember Simple Auth comes with and implement the persist, restore and clear methods:

pp/session-stores/application.js
rt Base from 'ember-simple-auth/session-stores/base';

rt default Base.extend({
rsist() {
?


store() {
?
FastBoot

Ember Simple Auth works with FastBoot out of the box as long as the Cookie session store is being used. In order to enable the cookie store, define it as the application store:

pp/session-stores/application.js
rt CookieStore from 'ember-simple-auth/session-stores/cookie';

rt default CookieStore.extend();

If you are using the OAuth2PasswordGrantAuthenticator, or DeviseAuthenticator, you must add node-fetch to your list of FastBoot whitelisted dependencies in package.json:


astbootDependencies": [
"node-fetch"
Testing

Ember Simple Auth comes with a set of test helpers that can be used in acceptance tests:

The test helpers can be imported from the helpers/ember-simple-auth module in the application's namespace:

ests/acceptance/?
rt { currentSession, authenticateSession, invalidateSession } from '<app-name>/tests/helpers/ember-simple-auth';
Other guides
License

Ember Simple Auth is developed by and © simplabs GmbH and contributors. It is released under the MIT License.

Ember Simple Auth is not an official part of Ember.js and is not maintained by the Ember.js Core Team.

This work is supported by the National Institutes of Health's National Center for Advancing Translational Sciences, Grant Number U24TR002306. This work is solely the responsibility of the creators and does not necessarily represent the official views of the National Institutes of Health.