The specification, template, and tests for creating an le-store- strategy for Let's Encrypt v2 / ACME using greenlock.js.
Go to file
AJ ONeal d657afbac9 show test #, stack, and stringified test 2016-08-13 15:04:33 -06:00
tests show test #, stack, and stringified test 2016-08-13 15:04:33 -06:00
.gitignore Initial commit 2016-08-11 23:20:20 -06:00
LICENSE Initial commit 2016-08-11 23:20:20 -06:00
README.md varname fix 2016-08-13 14:49:21 -06:00
index.js reference implementation 2016-08-13 14:48:55 -06:00

README.md

le-store-SPEC

The reference implementation, specification, template, and tests for creating an le-store- strategy.

The reference implementation is completely in-memory.

See Help Wanted: Database Plugins (for saving certs)

API

* getOptions()
* accounts.
  * checkKeypair(opts, cb)
  * setKeypair(opts, keypair, cb)
  * check(opts, cb)
  * set(opts, reg, cb)
* certificates.
  * checkKeypair(opts, cb)
  * setKeypair(opts, keypair, cb)
  * check(opts, cb)
  * set(opts, certs, cb)

Keypairs

For convenience, the keypair object will always contain both PEM and JWK versions of the private and/or public keys when being passed to the *Keypair functions.

set

setKeypair will always be called with email and all three forms of the keypair: privateKeyPem, publicKeyPem, and privateKeyJwk. It's easy to generate publicKeyJwk from privateKeyJwk because it is just a copy of the public fields e and n.

check

checkKeypair may be called with any of email, accountId, and keypair - which will contain only publicKeyPem and publicKeyJwk.