Skip to main content

Akamai Edge DNS Authenticator plugin for Certbot

Project description

Akamai Edge DNS Authenticator plugin for Certbot.

This plugin automates the process of completing a dns-01 challenge by creating, and subsequently removing, TXT records using the Akamai Edge DNS.

Configuration of EdgeDNS

The Akamai Edge DNS certbot plugin utilizes the Akamai OPEN Edge DNS API. To facilitate access, the plugin uses the standard Akamai OPEN credentials file, .edgerc. By default, This file is typically located in your HOME directory.

The Akamai OPEN credentials file location, and the section, must be specified in the certbot credentials file described in the following sections. Alternatively, The individual Akamai OPEN credential keys and values can be specified in the certbot credentials file as described in the following sections.

To set up your Akamai OPEN CREDENTIALS, and .edgerc file, see the authorization and credentials sections of the Akamai Developer Get Started guide.

Installation

Note: Python 3.12 or higher is required due to dependency requirements.

pip install certbot-plugin-edgedns

Named Arguments

To start using DNS authentication for edge DNS, pass the following arguments on certbot’s command line:

Argument

Description

--authenticator edgedns

Select the authenticator plugin (Required)

--edgedns-credentials

Akamai EdgeDNS Auth credentials INI file. (Required)

--edgedns-propagation-seconds

Waiting time for DNS to propagate before asking the ACME server to verify the DNS record. (Default: 180, Recommended: >= 600)

Credentials

An example credentials.ini file using Open Edgegrid keys directly:

client_token = akab-mnbvcxzlkjhgfdsapoiuytrewq1234567
access_token = akab-1234567890qwerty-asdfghjklzxcvtnu
client_secret = abcdefghijklmnopqrstuvwxyz1234567890ABCDEFG=
host = akab-aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.luna.akamaiapis.net
account_key = 1-2ABCD3 (OPTIONAL)

An example credentials.ini file using Open Edgegrid .edgerc file:

edgerc_path = /home/testuser/.edgerc
edgerc_section = default

The path to this file can be provided interactively or using the --edgedns-credentials command-line argument. Certbot records the path to this file for use during renewal, but does not store the file’s contents.

CAUTION: You should take proactive steps to protect these API credentials. Users who can read this file can use these credentials to issue arbitrary API calls on your behalf. Users who can cause Certbot to run using these credentials can complete a dns-01 challenge to acquire new certificates or revoke existing certificates for associated domains, even if those domains aren’t being managed by this server.

Certbot will emit a warning if it detects that the credentials file can be accessed by other users on your system. The warning reads “Unsafe permissions on credentials configuration file”, followed by the path to the credentials file. This warning will be emitted each time Certbot uses the credentials file, including for renewal, and cannot be silenced except by addressing the issue (e.g., by using a command like chmod 600 to restrict access to the file).

Examples

To acquire a single certificate for both example.com and *.example.com, waiting 900 seconds for DNS propagation:

certbot certonly \
  --csr ./example.com.pem \
  --authenticator edgedns \
  --edgedns-credentials /etc/letsencrypt/.secrets/domain.tld.ini \
  --edgedns-propagation-seconds 900 \
  --server https://acme-v02.api.letsencrypt.org/directory \
  --agree-tos \
  --rsa-key-size 4096 \
  -d 'example.com' \
  -d '*.example.com'

Docker

In order to create a docker container with a certbot-dns-edgedns installation, create an empty directory with the following Dockerfile:

FROM certbot/certbot
RUN pip install certbot-plugin-edgedns

Proceed to build the image:

docker build -t certbot/edgedns .

Once that’s finished, the application can be run as follows:

docker run --rm \
   -v /var/lib/letsencrypt:/var/lib/letsencrypt \
   -v /etc/letsencrypt:/etc/letsencrypt \
   --cap-drop=all \
   certbot/edgedns certonly \
   --authenticator edgedns \
   --edgedns-propagation-seconds 900 \
   --edgedns-credentials /etc/letsencrypt/.secrets/domain.tld.ini \
   --keep-until-expiring --non-interactive --expand \
   --server https://acme-v02.api.letsencrypt.org/directory \
   --agree-tos \
   -d example.com -d '*.example.com'

It is strongly suggested that the folder be secured by taking the following steps:

  1. chown root:root /etc/letsencrypt/.secrets

  2. chmod 600 /etc/letsencrypt/.secrets

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

certbot_plugin_edgedns-0.2.0.tar.gz (18.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

certbot_plugin_edgedns-0.2.0-py3-none-any.whl (13.8 kB view details)

Uploaded Python 3

File details

Details for the file certbot_plugin_edgedns-0.2.0.tar.gz.

File metadata

  • Download URL: certbot_plugin_edgedns-0.2.0.tar.gz
  • Upload date:
  • Size: 18.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.12

File hashes

Hashes for certbot_plugin_edgedns-0.2.0.tar.gz
Algorithm Hash digest
SHA256 fec65bad6a75c72fb8fed2dd2398174bedaed0421e9e82ea6743873799870913
MD5 e2acfb42e14131e5318d60804d11e87b
BLAKE2b-256 566a1550a9cc9a6ff117d45e1021439e957f72860d2a52c1d89c05674114a921

See more details on using hashes here.

File details

Details for the file certbot_plugin_edgedns-0.2.0-py3-none-any.whl.

File metadata

File hashes

Hashes for certbot_plugin_edgedns-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 55c78b6674ac01f0c04dcf881edad32dcf56891bf407742c251cad45309bc2ae
MD5 23d276b974f8834ee3b6b2dc7396bd99
BLAKE2b-256 cae3b6ae2349dda508e3aea6c6ee7237d919a68c2a65cff1bcb43d99e0e7f837

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page