Results for acm-client

Client for the ACME protocol.

CLI tool to obtain certificates via ACME and update the matching TLSA records. The primary authentication method is http-01 via webroot for now, but dns-01 is supported too.

Provides a client library for interacting with the acme-manager server (https://github.com/catphish/acme-manager) which assists with issuing lets-encrypt certificates

Acmesmith is an [ACME (Automatic Certificate Management Environment)](https://github.com/ietf-wg-acme/acme) client that works perfect on environment with multiple servers. This client saves certificate and keys on cloud services (e.g. AWS S3) securely, then allow to deploy issued certificates onto your servers smoothly. This works well on [Let's encrypt](https://letsencrypt.org).

This is the simple REST client for ACME DNS API V1. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the ACME DNS API, but note that some services may provide a separate modern client that is easier to use.

slim ACME (e. g. letsencrypt) client for quickly authorizing (multiple) domains and issuing certificates

**** letsencrypt-plugin gem has been renamed to acme-plugin, please use acme-plugin instead**letsencrypt-plugin is a Ruby on Rails helper for Let's Encrypt service for retrieving SSL certificates (without using sudo, like original letsencrypt client does). It uses acme-client gem for communication with Let's Encrypt server.

acme-plugin is a Ruby on Rails helper for ACME protocol services, ie. Let's Encryptfor retrieving SSL certificates (without using sudo, like original letsencrypt client does). It uses acme-client gem for communication with ACME protocol server.

The Public Certificate Authority API may be used to create and manage ACME external account binding keys associated with Google Trust Services' publicly trusted certificate authority. Note that google-cloud-security-public_ca-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-security-public_ca instead. See the readme for more details.

Redis::Directory assumes a Redis installation running on a default port and database 0 that will contain connection information for various other Redis databases. For example, if you were using a Redis database to store the content of cached pages, and this was running on a cluster of two Redis instances, with multiple applications connecting partitioned by database, then your connection might look like this: require "redis" require "redis/distributed" # The ACME Corp database is #27 cache = Redis::Distributed.new "redis://redis.example:4400/27", "redis://redis.example:4401/27" Redis::Directory uses a centralized Redis database to store the connection information so you don't have to remember "magic numbers" for each client/database mapping, and can easily update port-numbers/hostnames, cluster-members as necessary. The same connection with Redis::Directory would look like this: require "redis_directory" cache = Redis::Directory.new("redis.example").connect("cache", "acme")

No description provided.