letsencrypt-rails-heroku icon indicating copy to clipboard operation
letsencrypt-rails-heroku copied to clipboard

Published 20 hours ago • verified publisher icon pixielabs

Support alternative challenge methods

Open jalada opened this issue 5 years ago • 0 comments

There's lots of discussion about supporting DNS validations instead of HTTP validations, because it comes with the added benefit of working with wildcard domains.

However, DNS validations require programmatic DNS updates (e.g. via an API), and support for that is sporadic. Last time we checked there's no unified library for handling DNS updates, but if/when that changes we'd consider implementing this. We're not going to add individual API support (e.g. Cloudflare API, Route53 API) to letsencrypt-rails-heroku, that road leads to high-maintenance madness.

Related issues, PRs, and discussions: https://github.com/pixielabs/letsencrypt-rails-heroku/issues/59, https://github.com/pixielabs/letsencrypt-rails-heroku/pull/60, https://github.com/pixielabs/letsencrypt-rails-heroku/pull/62, https://github.com/pixielabs/letsencrypt-rails-heroku/issues/69

jalada avatar Oct 07 '20 11:10 jalada