single sign-on offline key server using asymmetric crypto in the browser with hyperboot for caching
To get your own keyboot server up and running, just do:
$ npm install -g keyboot
$ keyboot server -p 8000
For a full working example, consult:
and the keyboot-example-app source code.
To build applications that talk to keyboot, you can use these methods from your browser code.
var keyboot = require('keyboot')
Connect to the keyboot app running at url
in a hidden iframe.
Request opts.permissions
, an array of permissions that map to methods
available on kb
:
'sign'
'fingerprint'
'publicKey'
Sign a string or array buffer text
.
cb(err, res)
fires with an error or a Uint8Array signed blob res
.
Request a fingerprint.
cb(err, hash)
fires with an error or the fingerprint hash
that uniquely
identifies the user by the hash of their public key.
Request the user's public key.
cb(err, pubkey)
fires with an error or a json web key (JWK) for the user's
public key.
The keyboot interface sets up an event bus internally using page-bus that emits events for authorization state changes.
Emitted when the authorization request was approved.
Emitted when the authorization request was rejected.
Emitted when previously-accepted access is revoked.
Emitted when the instance is waiting for an answer to the access request from the remote keyboot app.
This is a good time to show the user a link to the keyboot url so they can approve the application.
This package ships with a keyboot
command for quickly starting up a server:
keyboot server { -p PORT, -d DIR, --verbose }
Start a keyboot server on PORT, writing hyperboot files to DIR.
If --verbose, print each http request.
With npm, to get the library do:
$ npm install keyboot
and to get the keyboot command do:
$ npm install -g keyboot
or you can fetch a pre-built version of the browser library with browserify cdn:
http://wzrd.in/standalone/keyboot@latest
MIT