Ember Simple Auth supports all Ember.js versions starting with 3.0.
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.
Basic Information
Usage
Core Feature Guides
Other Guides
Other Resources
- it maintains a client side session and synchronizes its state across multiple tabs/windows of the application
- it authenticates the session against the application's own server, external providers like Facebook etc.
- it is easily customizable and extensible
Ember Simple Auth consists of 3 main building blocks - the session, a session store and authenticators.
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.
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
git clone https://github.com/simplabs/ember-simple-auth.git
cd ember-simple-auth
yarn install && ember serve
and go to http://localhost:4200.
Installing the library is as easy as:
ember install ember-simple-authThe 3.0 release of ember-simple-auth removes previously deprecated code, introducing some breaking changes, but thankfully there is an upgrade guide.
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:
// app/controllers/application.js
import Controller from '@ember/controller';
import { inject as service } from '@ember/service';
export default Controller.extend({
session: service()
…
});In the invalidateSession action call the
session service's invalidate method
to invalidate the session and log the user out:
// app/controllers/application.js
import Controller from '@ember/controller';
import { inject as service } from '@ember/service';
export default Controller.extend({
session: service(),
…
actions: {
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.:
// app/authenticators/oauth2.js
import OAuth2PasswordGrant from 'ember-simple-auth/authenticators/oauth2-password-grant';
export default OAuth2PasswordGrant.extend();With that authenticator and a login form like
the session can be authenticated with the
session service's authenticate method:
// app/controllers/login.js
import Controller from '@ember/controller';
import { inject as service } from '@ember/service';
export default Controller.extend({
session: service(),
actions: {
async authenticate() {
let { identification, password } = this.getProperties('identification', 'password');
try {
await this.session.authenticate('authenticator:oauth2', identification, password);
} catch(error) {
this.set('errorMessage', error.error || error);
}
if (this.session.isAuthenticated) {
// What to do with all this success?
}
}
}
});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:
// app/routes/application.js
import Route from '@ember/routing/route';
import ApplicationRouteMixin from 'ember-simple-auth/mixins/application-route-mixin';
export default 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:
// app/routes/protected.js
import Route from '@ember/routing/route';
import AuthenticatedRouteMixin from 'ember-simple-auth/mixins/authenticated-route-mixin';
export default 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:
// app/router.js
Router.map(function() {
this.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:
// app/router.js
Router.map(function() {
this.route('login');
this.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 requests, you can use the session service to check if the session is authenticated and access authentication/authorization data, e.g. a token.
We provide the DataAdapterMixin for Ember Data adapters, that injects the session service
and also makes sure the session is invalidated if any of the requests returns an unauthorized response.
It can be used as:
// app/adapters/application.js
import DS from 'ember-data';
import DataAdapterMixin from 'ember-simple-auth/mixins/data-adapter-mixin';
import { computed } from '@ember/object';
const { JSONAPIAdapter } = DS;
export default JSONAPIAdapter.extend(DataAdapterMixin, {
headers: computed('session.data.authenticated.access_token', function() {
let headers = {};
if (this.session.isAuthenticated) {
// OAuth 2
headers['Authorization'] = `Bearer ${this.session.data.authenticated.access_token}`;
}
return headers;
}),
});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.:
this.get('session').set('data.locale', 'de');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:
this.get('session').authenticate('authenticator:some');Ember Simple Auth comes with 4 authenticators:
OAuth2PasswordGrantAuthenticator: an OAuth 2.0 authenticator that implements the "Resource Owner Password Credentials Grant Type"OAuth2ImplicitGrantAuthenticator: an OAuth 2.0 authenticator that implements the "Implicit Grant Type"DeviseAuthenticator: an authenticator compatible with the popular Ruby on Rails authentication plugin deviseToriiAuthenticator: an authenticator that wraps the torii library
To use any of these authenticators in an application, define a new
authenticator in app/authenticators, extend if from the Ember Simple Auth
authenticator
// app/authenticators/oauth2.js
import OAuth2PasswordGrantAuthenticator from 'ember-simple-auth/authenticators/oauth2-password-grant';
export default OAuth2PasswordGrantAuthenticator.extend();and invoke the session service's authenticate method with the respective
name, specifying more arguments as needed by the authenticator:
this.get('session').authenticate('authenticator:some', data);Authenticators are easily customized by setting the respective properties, e.g.:
// app/authenticators/oauth2.js
import OAuth2PasswordGrantAuthenticator from 'ember-simple-auth/authenticators/oauth2-password-grant';
export default OAuth2PasswordGrantAuthenticator.extend({
serverTokenEndpoint: '/custom/endpoint'
});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:
// app/authenticators/custom.js
import Base from 'ember-simple-auth/authenticators/base';
export default Base.extend({
restore(data) {
…
},
authenticate(options) {
…
},
invalidate(data) {
…
}
});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:
// app/session-stores/application.js
import Cookie from 'ember-simple-auth/session-stores/cookie';
export 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.
Ember Simple Auth comes with 4 stores:
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.
The localStorage store
stores its data in the browser's localStorage. This is used by the adaptive
store if localStorage is available.
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.
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.
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.
The session store is easily customized by setting the respective properties, e.g.:
// app/session-stores/application.js
import AdaptiveStore from 'ember-simple-auth/session-stores/adaptive';
export default AdaptiveStore.extend({
cookieName: 'my-apps-session-cookie'
});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:
// app/session-stores/application.js
import Base from 'ember-simple-auth/session-stores/base';
export default Base.extend({
persist() {
…
},
restore() {
…
}
});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:
// app/session-stores/application.js
import CookieStore from 'ember-simple-auth/session-stores/cookie';
export 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:
{
"fastbootDependencies": [
"node-fetch"
]
}Ember Simple Auth comes with a set of test helpers that can be used in acceptance tests.
Our helpers use the more modern testing syntax
and therefore require ember-cli-qunit 4.2.0 or greater
or ember-qunit 3.2.0 or greater.
We provide the following helpers:
currentSession()returns the current session.authenticateSession(sessionData)authenticates the session asynchronously; the optionalsessionDataargument can be used to mock the response of an authentication request, to provide a specific authorization token or user data.invalidateSession()invalidates the session asynchronously.
Which can be used as shown in the following example:
import { module, test } from 'qunit';
import { visit, currentURL } from '@ember/test-helpers';
import { setupApplicationTest } from 'ember-qunit';
import { currentSession, authenticateSession, invalidateSession } from 'ember-simple-auth/test-support';
module('Acceptance | app test', function(hooks) {
setupApplicationTest(hooks);
test('/login redirects to index if user is alread logged in', async function(assert) {
await authenticateSession({
authToken: '12345',
otherData: 'some-data'
});
await visit('/login');
assert.equal(currentURL(), '/');
let sessionData = currentSession().get('data.authenticated');
assert.equal(sessionData.authToken, '12345');
assert.equal(sessionData.otherData, 'some-data');
});
test('/protected redirects to /login if user is not logged in', async function(assert) {
await invalidateSession();
await visit('/protected');
assert.equal(currentURL(), '/login');
});
});If you're an ember-mocha user, we can recommend to check out this
example from the test suite of ember-simple-auth itself.
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.