esnet / esnet/acme-proxy

External TLS cert for acme-proxy

Open
#62 3 comments 0 reactions 1 assignee Claimed by @netops2devops View on GitHub
question
Dominant language
Go
Stars
58
Forks
7
Avg merge
1m
Merged PRs (30d)
1

Description

I am interested in using acme-proxy to centralize/secure the EAB credentials needed to get commercial certificates from Digicert. However I'd prefer that acme-proxy not use Digicert for it's own certificate. It would be really nice if we could provide our own cert/key for acme-proxy to us. Would it be possible to allow users to optionally specify a path to an existing certificate/key, rather than assume that acme-proxy is responsible for managing it's own cert?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.