A Seneca.js Auth Plugin
A user authentication plugin, using PassportJS for Express and Bell for Hapi.
Lead Maintainers: Mircea Alexandru and Mihai Dima
For a gentle introduction to Seneca itself, see the senecajs.org site.
If you're using this plugin module, feel free to contact me on twitter if you have any questions! :) @rjrodger
Supports Seneca versions 1.x - 3.x
npm install seneca-auth
Please see below the migration guide from older version to 0.4.x or above version.
A large part of the internal functionality of seneca-auth is now implemented as external plugins. Some of them are loaded by default in order to offer the basic functionality, some must be loaded explicitly.
Functionality | Loaded by default | plugin |
---|---|---|
Local strategy auth | Yes | seneca-local-auth |
Facebook strategy auth | No | seneca-facebook-auth |
Github strategy auth | No | seneca-github-auth |
Google strategy auth | No | seneca-google-auth |
LinkedIn strategy auth | No | seneca-linkedin-auth |
Twitter strategy auth | No | seneca-twitter-auth |
Redirect | Yes | auth-redirect |
Cookie token | Yes | auth-token-cookie |
Header token | No | auth-token-header |
Url matcher | Yes | auth-urlmatcher |
Restrict Login | No | auth-restrict-login |
Check the documentation of each plugin for details.
Disable default plugins by setting the flags on options.default_plugins
to false. For example, if you want to use auth-token-header instead of auth-token-cookie:
seneca.use(require('seneca-auth', {
default_plugins: { authTokenCookie: false }
})
seneca.use(require('auth-token-header'))
Hapi is supported only if using node 4 or greater. When using node 0.1x only Express is supported.
Some options are no longer supported:
service
- the service array that defines the auth strategies is no longer supported. Instead of this the auth strategies plugins must be loaded explicitly, each with its own options.sendemail
- the send email option (and send email functionality) is no longer supported.email
- see aboveWhen one of these parameters are provided to seneca-auth it will be considered a fatal error. Please remove them from seneca-auth options and check the documentation.
Some options are deprecated:
tokenkey
- this parameter is deprecated. It is now an option for one of the two plugins that are used for storing/retrieving the auth-token from request/response - auth-token-cookie or auth-token-headerDifferent conditions for login can be added by simply overriding the default behavior of seneca action with pattern:
role: 'auth', restrict: 'login'
This function must return:
{ ok: true }
in case that login is allowed based on the implemented rules{ ok: false, why: 'reason' }
in case that login is not allowed based on the implemented rules.An example of this implementation is provided by the plugin auth-restrict-login. The restrict condition implemented by this plugin is based on the existence of a cookie value in the request.
If more conditions are required these can be implemented in separated seneca actions. All actions can then be added to seneca but make sure
to call seneca.prior
from each action to make sure that all conditions in the chain are verified.
NOTE: Take a look at the user accounts example or seneca-mvp example.
The redirect functionality is now implemented as a separate module. Please see auth-redirect documentation for details.
The redirect module is loaded by default by seneca-auth.
Login an existing user and set a login token. A new login entity is created for each login.
/auth/login
urlpath.login
Logout an existing user with an active login. The login entity is updated to reflect the end of the login.
/auth/logout
urlpath.logout
Get the details of an existing, logged in user.
/auth/user
urlpath.user
This was previously the /auth/instance
.
Register a user and login automatically.
/auth/register
urlpath.register
cmd: register
documentation for details.Create a reset token
/auth/create_reset
urlpath.create_reset
cmd: create_reset
documentation for details.Note: The response will not contain reset token or user data. The client of this application should make sure to re-define this action and send email to the user with reset token.
Load a user entity using a reset token.
/auth/load_reset
urlpath.load_reset
cmd: load_reset
documentation for details.Execute a password reset action.
/auth/execute_reset
urlpath.execute_reset
cmd: execute_reset
documentation for details.Update user data.
/auth/update_user
urlpath.update_user
cmd: update_user
documentation for details.Change user password.
/auth/change_password
urlpath.change_password
cmd: change_password
documentation for details.var _ = require('lodash')
var Chairo = require('chairo')
var Hapi = require('hapi')
var Bell = require('bell')
var Hapi_Cookie = require('hapi-auth-cookie')
var server = new Hapi.Server()
server.connection({port: 3000})
server.register([Hapi_Cookie, Bell, Chairo], function (err) {
var si = server.seneca
si.use('user')
si.use('entity')
si.use(
require('seneca-auth'),
{
secure: true,
restrict: '/api'
}
)
si.add({role: 'test', cmd: 'service'}, function (args, cb) {
return cb(null, {something: 'else'})
})
si.act({
role: 'web',
plugin: 'test',
use: {
prefix: '/api',
pin: {role: 'test', cmd: '*'},
map: {
service: {GET: true}
}
}
}, function(err){
server.start(function () {
console.log(server.info.uri)
})
})
})
The Senecajs org encourages open participation. If you feel you can help in any way, be it with documentation, examples, extra testing, or new features please get in touch.
npm test
Copyright (c) 2012 - 2016, Richard Rodger and other contributors. Licensed under MIT.