Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certbot-like ability to update domains in a certificate (--expand) #123

Open
JayH5 opened this issue Aug 30, 2017 · 0 comments
Open

Certbot-like ability to update domains in a certificate (--expand) #123

JayH5 opened this issue Aug 30, 2017 · 0 comments

Comments

@JayH5
Copy link
Contributor

JayH5 commented Aug 30, 2017

This is mostly dependent on SAN support (#37).

We would like to be able to:

  1. Issue a single certificate for multiple domains (SAN)
  2. Change the domains (add/remove) for the certificate over time

See the Certbot documentation on re-creating and updating existing certificates.

This complicates things in terms of identifying certificates. Currently txacme identifies certificates by "server name", which is currently (although doesn't have to be), the common name (CN). Once there is SAN support, a certificate can be uniquely identified by all its domains CN + SAN (although I'm not sure if the order of those domains matters). So, on the surface, identifying a cert by its SANs seems reasonable. The problem is once you want to change the SANs in a cert, then you have a new list of domains and can't identify the old cert.

The first two ways I can think of to solve this are:

  • Identify certificates by CN. This then means that multiple certificates are not allowed with the same CN.
  • Use some other user-specified identifier for the certificate. Something like Certbot's --cert-name option (see Managing Certificates).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant