MarekSuchanek
commented
6 years ago Looks like it uses DNS challenge (which will be a bit bothersome for us since we do not have admin account to our domain 😢)... But we can try... What wildcard certificate we want to have (@janslifka. @vknaisl)? Just *.dsw.fairdata.solutions?
I can try to work on this without breaking the other certs... Also, for the main instance, we might want to use classical certs as now, because those should be seen as more secure. So the *.dsw.fairdata.solutions can be used for "less-important" services, testing/workshop instances, etc., to lower the administration overhead and to fight the rate limits for certificate renewals...
Other options is to have multiple domain names in one single certificate (up to 100). Obviously, this solution needs to know the names before hand unlike wildcard certs.
What should be done?
- Get wildcard
*.dsw.fairdata.solutionsbut use existing single-domain certs for core services (app.,api.,mail., etc.) - Get wildcard
*.dsw.fairdata.solutionsand multi-domain cert for core services (app.,api.,mail., etc.) - Get just single-domain and multi-domain certs grouped by instances of the wizard and services
- Nothing, leave it as is (just single-domain, and fight the complexity by using ☕️)
vknaisl
We have many subdomains for dsw.fairdata.solutions and we want HTTPS for everything. Wildcard certificate(s) are suitable...