Cool Solution - Let's Encrypt
From Univention Wiki
Note: Cool Solutions are articles documenting additional functionality based on Univention products. Packages provided by a Cool Solutions Repository are built by Univention, but will not be maintained.
Not all of the shown steps in the article are covered by Univention Support. For questions about your support coverage contact your contact person at Univention before you want to implement one of the shown steps.
This article explains how to install a small Let's Encrypt client using the "ACME" protocoll by running a wrapper script, which UCR variables must be configured and how to obtain the certificates.
Installation
After installing the package univention-letsencrypt the client is ready for configuration:
1 univention-install univention-letsencrypt
Prerequisite
The package brings a new UCR variable which is read by the wrapper script from univention-letsencrypt:
| UCR Variable | Description | Example |
|---|---|---|
letsencrypt/services/apache2 |
Whether the Apache2 webserver should be configured automatically or not, valid values are "Yes" or "No" | |
letsencrypt/services/postfix |
Whether the postfix service should be configured automatically or not, valid values are "Yes" or "No" | |
letsencrypt/services/dovecot |
Whether the dovecot service should be configured automatically or not, valid values are "Yes" or "No" | |
letsencrypt/domains |
Public reachable FQDN | server.example.com |
Obtaining the certificate
Run the script /usr/share/univention-letsencrypt/setup-letsencrypt to automatically register an account, create the needed files and start the certificate creation and validation for the domain saved in the UCR variable letsencrypt/domains. The script installs a cronjob that periodically checks if the certificate must be renewed. All actions from the script are written into a the log file /var/log/univention/letsencrypt.log.
The certificate is saved in the directory /etc/univention/letsencrypt.
At the end, setup-letsencrypt checks the three service UCR variables and, if one is found set to "Yes", runs the needed scripts from the setup.d and post-refresh.d directories to configure the Apache2 webserver, postfix, or dovecot. Additional services can be configured by placing appropriate configuration scripts into these directories.
