Import SSL Certificates
This section covers how to configure SSL certificate for new Uyuni installation, and how to replace existing certificates.
Before you begin, ensure you have:
A certificate authority (CA) SSL public certificate. If you are using a CA chain, all intermediate CAs must also be available.
An SSL server private key
An SSL server certificate
All files must be in PEM format.
The host name of the SSL server certificate must match the fully qualified host name of the machine you deploy them on.
You can set the host names in the
X509v3 Subject Alternative Name section of the certificate.
You can also list multiple host names if your environment requires it.
Supported Key types are
EC (Elliptic Curve).
Third-party authorities commonly use intermediate CAs to sign requested server certificates. In this case, all CAs in the chain are required to be available. If there is no extra parameter or option available to specify intermediate CAs, take care that all CAs (Root CA and intermediate CAs) are stored in one file.
By default, Uyuni uses a self-signed certificate. After you have completed the initial setup, you can replace the default certificate with an imported certificate.
Install the Uyuni Server according to the instructions in Installation.
Complete the initial setup according to SUSE Manager Server Setup.
At the command prompt, point the SSL environment variables to the certificate file locations:
export CA_CERT=<path_to_CA_certificates_file> export SERVER_KEY=<path_to_web_server_key> export SERVER_CERT=<path_to_web_server_certificate>
Complete Uyuni setup:
When you are prompted for certificate details during setup, fill in random values. The values are overridden by the values you specified at the command prompt.
By default, Uyuni Proxy uses a self-signed certificate. After you have completed the initial setup, you can replace the default certificate with an imported certificate.
Use the same certificate authority to sign all server certificates for servers and proxies. Certificates signed with different CAs do not match.
You can replace active certificates on your Uyuni installation with a new certificate. To replace the certificates, you can replace the installed CA certificate with the new CA, and then update the database.
On the Uyuni Server, at the command prompt, call the command
mgr-ssl-cert-setupand provide the certificates as parameters:
mgr-ssl-cert-setup --root-ca-file=<Path_to_Root_CA_Certificate> --server-cert-file=<Server_Cert_File> --server-key-file=<Server_Key_File>
Intermediate CAs can either be available in the file which is specified with
--root-ca-file or specified as extra options with
--intermediate-ca-file option can be specified multiple times.
This command performs a number of tests on the provided files to test if they are valid and can be used for the requested use case.
Restart services to pick up the changes:
spacewalk-service stop systemctl restart postgresql.service spacewalk-service start
If you are using a proxy, you need to generate a server certificate RPM for each proxy, using their host names and cnames.
You should use
mgr-ssl-cert-setup also on a Uyuni Proxy to replace the certificates.
Because the Uyuni Proxy does not have a postgreSQL database, only
spacewalk-service restart is sufficient.
If the Root CA was changed, it needs to get deployed to all the clients connected to Uyuni.
In the Uyuni Web UI, navigate to.
Check all your Salt Clients to add them to the system set manager.
Statesfield, click Apply to apply the system states.
Highstatepage, click Apply Highstate to propagate the changes to the clients.
Traditional Clients are deprecated and should be replaced with Salt Client.
If the CA needs to be replaced when there are still traditional managed clients connected to Uyuni some extra steps are required.
Important is, that the clients do not get disconnected when the new CA is activated on the Uyuni Server and Proxies. Deploy the 'old' and the 'new' Root CA certificates to the affected clients and trust them. Use a configuration channel to deploy the certificte files to the clients and the remote command feature to regenerate the trust store.
After the new certificates are activated on the Uyuni Server and Proxies, test if the connections are working and actions can still be scheduled on the clients. If this is the case, the 'old' Root CA can be removed from clients.