Name: le-store-redis
Owner: Digital Bazaar, Inc.
Description: Redis certificate storage back-end for Node Let's Encrypt
Created: 2016-12-19 15:22:03.0
Updated: 2017-01-18 22:12:27.0
Pushed: 2016-12-26 22:23:43.0
Homepage: null
Size: 54
Language: JavaScript
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
The Redis storage strategy for node-letsencrypt is capable of storing and retrieving keypairs, accounts, certificates, and certificate keypairs from a Redis database. It is most useful in production setups where multiple load balancers need to provide HTTPS-based proxying for a number of application front-end systems.
It is strongly advised that any production Redis system is deployed using at least password-based authentication in addition to protections like IP-based request limiting and client-side TLS certificates. Unauthorized access to the Redis database enables an attacker to spoof any certificate stored in the database.
The following options may be set in the options
parameter:
`true
` if debug output is desired.To instantiate a Redis-based Let's Encrypt plugin:
configure Redis-based Let's Encrypt storage backend for storing keys and certs
r leStore = require('le-store-redis').create({
debug: true
redisOptions: {
db: 2,
password: 'M3C1lSO1kLBdPd95tJGu1I0OtTp4c5Rz'
}
;
This object may then be used in the Let's Encrypt constructor.
The Redis database is designed to be scalable to at least thousands of domains. Scalability past tens of thousands of domains has not been tested, but should work (in theory) based on the indexing layout and available memory.
There are three primary types of data that are stored in the database:
There are five types of indexes in the database: