DESEC_TOKEN and DEDYN_TOKEN

Henry · August 30, 2022, 2:25pm

Hello together,

maybe an info or a question.

I’m using a dedyn domain for a docker/traefik installation and for a proxmox server. For both i have retrieved a valid letsencrypt certificate with dns-01 challenge.

traefik used lego for the challenge
https://go-acme.github.io/lego/dns/desec/

proxmox used a module based on acme.sh for the challenge.

github.com

acmesh-official/acme.sh/blob/130e8dbd40b71a33dfb8adec7a7a681c2059a7a7/dnsapi/dns_desec.sh

#!/usr/bin/env sh
#
# deSEC.io Domain API
#
# Author: Zheng Qian
#
# deSEC API doc
# https://desec.readthedocs.io/en/latest/

REST_API="https://desec.io/api/v1/domains"

########  Public functions #####################

#Usage: dns_desec_add   _acme-challenge.foobar.dedyn.io   "d41d8cd98f00b204e9800998ecf8427e"
dns_desec_add() {
  fulldomain=$1
  txtvalue=$2
  _info "Using desec.io api"
  _debug fulldomain "$fulldomain"
  _debug txtvalue "$txtvalue"

This file has been truncated. show original

For traefik i have to use the DESEC_TOKEN environment variable and for proxmox i have to use the DEDYN_TOKEN environment variable.

I think the usage of different environment variables has “historic” reasons?

Regards, Henry

peter · August 30, 2022, 8:35pm

Hi Henry,

I would think so, yes.

On the deSEC side, API tokens are just API tokens – there is no distinction like DESEC_TOKEN and DEDYN_TOKEN. I wouldn’t even know what that would mean. It’s just a variable name and doesn’t mean anything, really.

Stay secure,
Peter