mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 04:45:48 +03:00
[GH-ISSUE #214] Using none LetsEncrypt ACME for auto enroll of TLS certs #98
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#98
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @oregano87 on GitHub (Mar 19, 2020).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/214
For using ACME-DNS with on-prem CAs with ACME it would be great to expand the tls options. Currently only "letsencrypt" and "letsencryptstaging" are possible values for automatic enrollment.
I would like to have an option like "acme-server" and another variable like "acme_directory_url".
@joohoi commented on GitHub (Mar 20, 2020):
Thanks for the suggestion. This is an easyish addition.
The main.go needs to have a case for the custom acme supporting ca, and a similar line that configures the used acme server should be pulled from a newly added configuration variable.
The url should point to the ACME server directory endpoint. For example the Let's Encrypt staging endpoint URL would be:
https://acme-staging-v02.api.letsencrypt.org/directory