This project was build, to handle Passwordless as a build in authentication method using the common authentication library Passport. By plugging into Passport, Passwordless can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express.
npm install passport-passwordless
yarn add passport-passwordless
passport.use(new PasswordlessStrategy({
//... configuration ...
}, function (req, user, done) {
//.. validate the logged in user and build your final user object
return done(null, user);
};
{
allowTokenReuse : true,
tokenLifeTime : 1000 * 60 * 10,
store : {
//This is used to require() the library needed
path: "", //Your passwordless store library. For MongoDB use something like passwordless-mongostore-bcryptjs.
config: {} //The configuration for the chosen library
},
delivery: (
tokenToSend: string,
uidToSend: string,
recipient: string,
callback: any,
req: any
) => {
//Send your token using whatever code you'd like and then use the callback function.
callback()
}
}
The path parameter for the store and delivery configuration is needed to exclude obsolete library dependencies of this package. So the delivery / store package can be required from the parent lib.
{
//If this property will be set to true, each authentication request generates a new passwordless instance to handle multiple and dynamic configurations
//If it's set to false, the passwordless instance will be created by instantiating the strategy
dynamicConfig : false,
//all passwordless internal parameters, that are used to parse the request query object
userField : 'user',
tokenField : 'tokenField',
uidField : 'uidField',
deliveryField : 'delivery',
originField : null,
//token relevant parameters
allowTokenReuse : true,
tokenLifeTime : 1000 * 60 * 10,
//specify maximal token length
maxTokenLength : 16,
//If you want to create your own token type use this function, to use your own algorithm.
//tokenAlgorithm : function() {
// Function shall return the token in sync mode (default: Base58 token)
//},
//includes the store configuration
//setup a path to the node_module that should be used
//setup a configuration array that will be applied to the store constructor
//internally it looks like the following code :
// var store = require(this.options.store.path);
// store(this.options.store.config);
store : {
path : __dirname + '/node_modules/passwordless-redis',
config : [
6379,
'127.0.0.1',
{
}
]
},
//Specify the delivery configurations
//following object contains an example with emailjs
//
//Notice : currently only a delivery for emailjs is written
// If you want to use another delivery, feel free to implement it or apply a function like the following as the delivery
// function(options) {
// var email = require(options.path);
// var smtp = email.server.connect(options.config.server);
//
// return function(tokenToSend, uidToSend, recipient, callback, req) {
// ... do delivery stuff..
// callback(err);
// };
// }
delivery :
},
//is used to check if an user is authorized to request a token
//call the callback with an error and an user object (user object needs an parameter called "id" to specify it's email adress, sms, ...)
//the default access functions contains the following function
access : function(user, callback) {
callback(null, user);
}
}
The MIT License (MIT) Copyright © 2016 Tschuck
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.