ISSUE MIGRATED FROM https://gitlab.com/aegir/hosting_https/issues/6 (see #2934484: Move back issue management to D.o)

The current choice of cert service is per server.
I can imagine having lets encrypt as default ... but what if a client comes along who want something else... EV?
It might be good to have certificates from multiple services on one server.

Just a though, feature request?

Jon Pugh @jonpugh commented 7 months ago

I've started work on refactoring these modules.

Created a new property "https_sign_method" on site nodes, added a radio button to let users select the method they wish to use for each site.

I think we can reduce the amount of code here greatly by consolidating Key/CSR creation in hosting_https.module, then just use the property http_sign_method to trigger either nothing, self signing, or LE signing. We should be able to remove the "Certificate" service type completely.

Here's what the UI looks like:

There's a merge request Refactor everything to allow per-site certificate generation for this

CommentFileSizeAuthor
Screenshot_from_2017-05-25_14-30-35.png144.09 KBhelmo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

helmo created an issue.