-
Notifications
You must be signed in to change notification settings - Fork 0
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
One SSL-Certificate for all our hosts #69
Comments
Hi @acka47 if you find a hostname missing in the list please add it and ping. |
I think we do not use |
I added metafacture.org and restructured the list to take into account Mariusz' advice to have on certificate per domain. |
Deployed, please test. Note that skohub and nwbib will be renewed at the end of the next year. |
+1 Closing. |
It's possible to only have one SSL-certificate for multiple hostnames SubjectAlternativeName, SAN. Since we use a proxy, allmost all hostnames we control point to it (empyhtos). It's far more simple to have just one certificate for certificates must be renewed regularly.
For a CSR we need a list of all these hostnames.
The hostnames in need of a valid SSL certificate are listed here. The list should be updated if needed:
FQDN: lobid.org
FQDN: www.lobid.org
FQDN: beta.lobid.org
FQDN: blog.lobid.org
FQDN: labs.lobid.org
FQDN: slides.lobid.org
FQDN: test.lobid.org
FQDN: metafacture.org
FQDN: www.metafacture.org
FQDN: nwbib.de
FQDN: www.nwbib.de
FQDN: test.nwbib.de
FQDN: skohub.io
FQDN: www.skohub.io
FQDN: test.skohub.io
Note: everytime this list is updated a new CSR must be done asking our IT to provide a new certificate. Also, of course, this must be done when the certificate is going to expire.
The text was updated successfully, but these errors were encountered: