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

Configure wildcard TLS certificate #7

Open
cbj4074 opened this issue Sep 19, 2018 · 1 comment
Open

Configure wildcard TLS certificate #7

cbj4074 opened this issue Sep 19, 2018 · 1 comment
Assignees
Labels
General General Documentation Issue Todo A Task

Comments

@cbj4074
Copy link
Member

cbj4074 commented Sep 19, 2018

Currently, the various domains use individual TLS certificates, which are cumbersome to renew (only because Let's Encrypt's automated renewal process is not without points of failure).

Overall, maintaining a single wildcard certificate will require less work and carry a lower risk of failure.

@cbj4074 cbj4074 self-assigned this Sep 19, 2018
@cbj4074
Copy link
Member Author

cbj4074 commented Sep 19, 2018

Actually, my initial assumption may be false.

Apparently, wildcard certificates are not trivial to maintain because they require authentication via the DNS-01 challenge type, which means that in order to fully-automate their renewal, it's necessary to be able to update the relevant DNS records programatically.

More info in the Wildcard Support announcement:

https://community.letsencrypt.org/t/acme-v2-and-wildcard-certificate-support-is-live/55579

Additionally, there are risks associated with configuration automated TXT record updates at the DNS provider, which are detailed in one of the replies to this how-to thread:

https://community.letsencrypt.org/t/wildcard-domain-step-by-step/58250/4

I suppose we'll need to meditate on this a bit before taking action, but either way, the renewal process, from our end, needs to be made more or less bulletproof.

@cbj4074 cbj4074 added the Todo A Task label Sep 19, 2018
@poppabear8883 poppabear8883 added Todo A Task General General Documentation Issue and removed Todo A Task labels Sep 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
General General Documentation Issue Todo A Task
Projects
None yet
Development

No branches or pull requests

2 participants