concorde is an ACMEv2 client in three parts:

1. concorde.shaman: a fully automated tool designed to sign TLS certificates with minimal setup required
2. concorde.cli: a not-so-user-friendly commandline ACME client tool that for when you need to do something manual
3. concorde.acme: a low-level Python 3 ACME client library that is used by both of the above packages

concorde has a lightweight dependency footprint: its immediate dependencies are the cryptography and requests libraries. concorde also completely defers authenticating authorization challenges to external programs. This allows it to run without requiring any special privileges.

concorde does not allow flexibility in choice of the signature algorithms used for account keys nor domain keys. It also prefers PEM format for persisting these to disk. This is intended to reduce the possibility of using poor algorithm choices.

shaman is designed to be a tool that is safe to run repeatedly to keep your certificates up to date.

Usage:

$ shaman [<profile>]

If <profile> is not specified, shaman, defaults to the current directory. All configuration is read from a file shaman.json in the profile directory. shaman will update this file as necessary.

The minimal file should look something like this:

{
    "server": "https://acme-v02.api.letsencrypt.org/directory",
    "renewal": 10,
    "authenticators": {
        "http-01": "prove-challenge"
    }
    "domains": {
        "example.com": {
        }
    }
}

Each piece in the configuration will be explained, by outlining what shaman will do:

1. look for a key property. If it doesn't exist:
   1. generate a new SECP384R1 account private key
   2. write that key to disk
   3. create a key property that refers to the location from the previous step
2. look for an account_id property. If it doesn't exist:
   1. create a new account on the specified server with the account key
   2. create an account_id property that refers to the location of the account created in the previous step
3. for each entry in the domain block:
   1. look for a key property. If it doesn't exist:
      1. generate a new SECP384R1 domain private key
      2. write that key to disk
      3. create a key property that refers to the location from the previous step
   2. look for either an order_id or a certificate_id key. If:
      • order_id exists:
        1. get the corresponding order object, and check its status:
           • if the order object is not found or its status is invalid:
             1. create a new order object for this domain
             2. update the order_id key in this domain
           • if it is pending:
             1. for each pending authorization in the order:
                1. for each challenge in the authorization`:
                   1. authorize the challenge using the account key
                   2. invoke the specified authenticator for this domain (falling back to a configuration-wide authenticator if a domain-specific authenticator is not found)
                   3. validate the challenge
                2. fail if none of the challenges can be satisfied with the specified authenticators
           • if it is ready:
             1. finalize the order with a CSR generated for this domain
           • if it is valid:
             1. fetch the certificate object for this order
             2. update the certificate_id key for this domain
             3. remove the order_id key for this domain
             4. update the on-disk certificate if needed
      • certificate_id exists:
        1. fetch the certificate object for this order
        2. check the certificate expiry date:
           • if it will expire within renewal days:
             1. delete the certificate_id property
             2. repeat the entire step for this domain
           • otherwise, update the on-disk certificate if needed
      • neither exist:
        1. create a new order object for this domain
        2. update the order_id key in this domain

The optional logThreshold can control the logging level used. It defaults to 20, but can be set to 10 or lower for more verbose logging.

Since shaman defers to 'authenticators' it doesn't need any special privileges to prove domain ownership, however it does mean that some additional set up is required. An authenticator is invoked with no arguments. Data is supplied to its standard input as follows (where <LF> is the ASCII Line Feed character or the 0x0A octet):

<token><LF><key_authorization><LF>

The authenticator is expected to perform whatever action is appropriate and exit with status code zero. Any other status code is regarded a failure to authenticate.

As an example of an authenticator, the following nginx server block:

server {
    listen 80;
    server_name ~(?<vhost>.*);

    location ~\/\.well-known\/acme-challenge\/(.*) {
        alias /mnt/acme-challenge/$1;
    }
}

would make the following bash script with executable permissions a valid authenticator:

#!/bin/bash

read token
read key_authorization

echo $key_authorization > /mnt/acme-challenge/$token

shaman logs its actions to '/dev/log' using the 'syslog' protocol as well as to standard out.

The commandline tool is purposefully a stateless and tedious tool to use, because it does not read any configuration files. It is strongly recommended to use shaman and only use the commandline tool if something manual needs to be done.

The tool has built-in help, but an overview of its commands are listed below:

concorde keys create <path>

concorde unreg <key> <server> create
concorde unreg <key> <server> status

concorde reg <key> <account id> <server> acct status
concorde reg <key> <account id> <server> acct update

concorde reg <key> <account id> <server> order create <type>|<value> [<type>|value>...]
concorde reg <key> <account id> <server> order status <order_id>
concorde reg <key> <account id> <server> order get-authz <order_id> <index>
concorde reg <key> <account id> <server> order finalize <order_id> <key> <value> [<value>...]
concorde reg <key> <account id> <server> order get-cert <order_id>

concorde reg <key> <account id> <server> challenge <challenge_id> status
concorde reg <key> <account id> <server> challenge <challenge_id> authorize
concorde reg <key> <account id> <server> challenge <challenge_id> validate

Install via pip:

$ python3 -m pip install git+https://github.com/frutiger/concorde.git

This will install the concorde and shaman scripts into Python's binary path.

Copyright (C) 2016 Masud Rahman

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.