- move license section to separate file - remove examples, api documentation is enough for now
Node One Time Password library
Simple to use, fast, and with zero dependencies. The Node One Time Password library is fully compliant with HOTP (counter based one time passwords) and TOTP (time based one time passwords). It can be used in conjunction with the Google Authenticator which has free apps for iOS, Android and BlackBerry.
Installation
npm install notp
Usage
var notp = require('notp');
//.... some initial login code, that receives the user details and TOTP / HOTP token
var key = 'secret key for user... could be stored in DB';
var token = 'user supplied one time use token';
// Check TOTP is correct (HOTP if hotp pass type)
var login = notp.totp.verify(token, key);
// invalid token if login is null
if (!login) {
return console.log('Token invalid');
}
// valid token
console.log('Token valid, sync value is %s', login.delta);
Google Authenticator
Google authenticator requires that keys be base32 encoded before being used. This includes manual entry into the app as well as preparing a QR code URI.
To base32 encode a utf8 key you can use the thirty-two
module.
var base32 = require('thirty-two');
var key = 'secret key for the user';
// encoded will be the secret key, base32 encoded
var encoded = base32.encode(key);
// to create a URI for a qr code (change totp to hotp is using hotp)
var uri = 'otpauth://totp/somelabel?secret=' + encoded;
Note: If your label has spaces or other invalid uri characters you will need to encode it accordingly using encodeURIComponent
More details about the uri key format can be found on the google auth wiki
API
##hotp.verify(token, key, opt)
Check a One Time Password based on a counter.
First argument of callback is true if password check is successful,
or false if check fails.
Second argument is the time step difference between the client and
the server. This argument is only passed if the password check is
successful.
Arguments:
opt
window - The allowable margin for the counter. The function will check
W codes in the future against the provided passcode. Note,
it is the calling applications responsibility to keep track of
W and increment it for each password check, and also to adjust
it accordingly in the case where the client and server become
out of sync (second argument returns non zero).
E.g. if W = 100, and C = 5, this function will check the psscode
against all One Time Passcodes between 5 and 105.
Default - 50
counter - Counter value. This should be stored by the application, must
be user specific, and be incremented for each request.
##totp.verify(token, key, opt)
Check a One Time Password based on a timer.
First argument of callback is true if password check is successful,
or false if check fails.
Second argument is the time step difference between the client and
the server. This argument is only passed if the password check is
successful.
Arguments:
opt
window - The allowable margin for the counter. The function will check
W codes either side of the provided counter. Note,
it is the calling applications responsibility to keep track of
W and increment it for each password check, and also to adjust
it accordingly in the case where the client and server become
out of sync (second argument returns non zero).
E.g. if W = 5, and C = 1000, this function will check the psscode
against all One Time Passcodes between 995 and 1005.
Default - 6
time - The time step of the counter. This must be the same for
every request and is used to calculat C.
Default - 30
##hotp.gen(key, opt)
Generate a counter based One Time Password
First argument of callback is the value of the One Time Password
Arguments:
opt
counter - Counter value. This should be stored by the application, must
be user specific, and be incremented for each request.
##totp.gen(key, opt)
Generate a time based One Time Password
First argument of callback is the value of the One Time Password
Arguments:
opt
time - The time step of the counter. This must be the same for
every request and is used to calculate C.
Default - 30