feathersjs
feathers-authentication-client
The authentication plugin for feathers-client
Installation
npm install feathers-authentication-client --saveNote: This is only compatibile with `feathers-authentication@1.x` and above.
Documentation
API
This module contains:
- The main entry function
- Some helpful hooks
The main feathers client instance has a few public methods:
app.authenticate(options)- Authenticate by passing credentials.app.logout()
It also has a app.passport instance that, like on the server, exposes utils functions for dealing with JWTs:
app.passport.getJWT()- pull it from localstorage or the cookieapp.passport.verifyJWT(token)- verify that a JWT is not expired and decode it to get the payload.
Note: All these methods return promises.
Handling the special re-authentication errors
In the event that your server goes down or the client loses connectivity, it will automatically handle attempting to re-authenticate the socket when the client regains connectivity with the server. In order to handle an authentication failure during automatic re-authentication you need to implement the following event listener:
const errorHandler = error => {
app.authenticate({
strategy: 'local',
email: 'admin@feathersjs.com',
password: 'admin'
}).then(response => {
// You are now authenticated again
});
};
// Handle when auth fails during a reconnect or a transport upgrade
app.on('reauthentication-error', errorHandler)Default Options
The following default options will be mixed in with the settings you pass in when configuring authentication. It will set the mixed options back to to the app so that they are available at any time by app.get('auth'). They can all be overridden.
{
header: 'Authorization', // the default authorization header
path: '/authentication', // the server side authentication service path
jwtStrategy: 'jwt', // the name of the JWT authentication strategy
entity: 'user', // the entity you are authenticating (ie. a users)
service: 'users', // the service to look up the entity
cookie: 'feathers-jwt', // the name of the cookie to parse the JWT from when cookies are enabled server side
storageKey: 'feathers-jwt', // the key to store the accessToken in localstorage or AsyncStorage on React Native
}Hooks
There are 3 hooks. They are really meant for internal use and you shouldn't need to worry about them very often.
populateAccessToken- Takes the token and puts in onhooks.params.accessTokenin case you need it in one of your client side services or hookspopulateHeader- Add the accessToken to the authorization headerpopulateEntity- Experimental. Populate an entity based on the JWT payload.
Complete Example
Here's an example of a Feathers client that uses feathers-authentication-client.
const feathers = require('feathers/client');
const rest = require('feathers-rest/client');
const superagent = require('superagent');
const hooks = require('feathers-hooks');
const localStorage = require('localstorage-memory');
const auth = require('feathers-authentication-client');
const client = feathers();
// NOTE: the order is important: auth must be configured _after_ rest/socket
client.configure(hooks())
.configure(rest('http://localhost:3030').superagent(superagent))
.configure(auth({ storage: localStorage }));
client.authenticate({
strategy: 'local',
email: 'admin@feathersjs.com',
password: 'admin'
})
.then(response => {
console.log('Authenticated!', response);
return client.passport.verifyJWT(response.accessToken);
})
.then(payload => {
console.log('JWT Payload', payload);
return client.service('users').get(payload.userId);
})
.then(user => {
client.set('user', user);
console.log('User', client.get('user'));
})
.catch(function(error){
console.error('Error authenticating!', error);
});License
Copyright (c) 2016
Licensed under the MIT license.