A memory-based strategy for node-letsencrypt for setting, retrieving, and clearing ACME challenges issued by the ACME server
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
AJ ONeal 7ad1ffdfdc fix typos 5 years ago
.gitignore Initial commit 8 years ago
LICENSE v2.0.1 5 years ago
README.md fix typos 5 years ago
index.js v2.1.1 5 years ago
package.json fix typos 5 years ago
test.js v2.0.0 8 years ago

README.md

| letsencrypt (library) | letsencrypt-cli | letsencrypt-express | letsencrypt-koa | letsencrypt-hapi |

le-challenge-memory

An in-memory strategy for node-letsencrypt for setting, retrieving, and clearing ACME challenges issued by the ACME server

  • Safe to use on ephemeral services (i.e. AWS)

Install

npm install --save le-challenge-standalone@2.x

Usage

var leChallenge = require('le-challenge-standalone').create({
, debug: false
});

var LE = require('greenlock');

LE.create({
  server: LE.stagingServerUrl
, challenge: leChallenge
});

NOTE: If you request a certificate with 6 domains listed, it will require 6 individual challenges.

Exposed Methods

For ACME Challenge:

  • set(opts, domain, key, val, done)
  • get(defaults, domain, key, done)
  • remove(defaults, domain, key, done)

Legal & Rules of the Road

Greenlock™ and Bluecrypt™ are trademarks of AJ ONeal

The rule of thumb is "attribute, but don't confuse". For example:

Built with Greenlock (a Root project).

Please contact us if you have any questions in regards to our trademark, attribution, and/or visible source policies. We want to build great software and a great community.

Greenlock™ | MPL-2.0 | Terms of Use | Privacy Policy