we have a list of supported challenge types per plugin, so we only need
one generic implementation.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
and move handling of tokens/key_auths to plugins, since it's not bound
to be identical for all challenge types forever.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
including the key authorization is deprecated and will be removed at
some point, might as well clean that up now to be prepared.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
At the moment, Proxmox has two different configurations that require different properties.
DNSChallange requires credentials for the DNSAPI.
Standalone has no settings because Letsencrypt only supports port 80 with the http-01 challenge.
This configuration is registered in the pve-manager.
Signed-off-by: Wolfgang Link <w.link@proxmox.com>
Copy the DNS plugins form acme.sh
The project acme.sh can be found here.
https://github.com/Neilpang/acme.sh
Signed-off-by: Wolfgang Link <w.link@proxmox.com>
acme.sh DNS plugins expect a configuration in which the login information
is stored.
We pass the credentials with the command.
This function supports the expected behavior of the plugins.
Signed-off-by: Wolfgang Link <w.link@proxmox.com>
This Code is not required in the Proxmox environment.
We know in our environment what we have as a tool-change.
Fix Code what does not work because variable or functions are missing.
Signed-off-by: Wolfgang Link <w.link@proxmox.com>
For the thin wrapper around acme.sh DNS plugins, the required functions are copied.
The project acme.sh can be found here.
https://github.com/Neilpang/acme.sh
Signed-off-by: Wolfgang Link <w.link@proxmox.com>
