How to recreate SMT 11 CA and server certificate
This document (7006024) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 12
SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 10
- Since YaST does not allow to delete the existing CA as long it has not expired, we have to delete the related files manually.
- Open up a shell and change to /var/lib/CAM and move the directory of the existing CA to /tmp/, e.g. by executing "mv YaST_Default_CA /tmp/". Attention: Do not move or delete the ".cas" directory. Do not move or delete the file openssl.cnf.tmpl either, as it's a template for YaST CA Management.
Create root CA
- From the root shell start 'yast2 ca_mgm'.
- Select 'Create Root CA'.
- For "CA Name" and "Common Name" enter "YaST_Default_CA". Please note not to use the server name or server FQDN in here, since this would complicate later error analysis!
- Enter the email address of the issuer (and select "add") and enter optional information such as organization, unit, locality, state and country.
- Select "Next".
- Choose the password, length of the key and its validity.
- Select "Next" to see an overview about the CA.
- Select "Create" to create the CA.
Create server certificate
- Select the newly created CA in the YaST2 CA management module.
- Press "Enter CA".
- Enter the CA password.
- Select the Certificates tab.
- Click on "Add" and choose Server Certificate.
- Provide the requested data:
- For Common Name put in the fully qualified domain name of the server (FQDN) of the server, for example "smt-server.example.net". This is mandatory!
- Add an valid email address of the server administrator and press "Add".
- Press "Next".
- Here it is possible to either use the CA password for the server certificate or a different one. Also key length and validity may be changed.
- Add DNS hostname and IP address to Subject Alternative Name. Adding the IP is optional, but the DNS hostname (as the FQDN) must be added, else the certificate will not accepted on all implementations. Adding the IP address has the advantage that clients also could use IP to connect to SMT server, but as IP might change, DNS hostname should be preferred . Add additional DNS hostnames and IP addresses of the SMT server if needed.
- Select 'Advanced Options'.
- Select 'Subject Alt Name' (not to be confused with Issuer Alt Name!!).
- Select 'Add'.
- Choose 'DNS' and put int the hostname (CN) of the server
- Choose 'IP' and put in the IP address of the server.
Export the certificate as common server certificate, so that the http server apache uses it
- On the certificates tab locate the "Export" button.
- Select "Export as common server certificate".
- Enter the password that was chosen for the server certificate.
- A message "Certificate has been written as common server certificate" will be displayed.
Export the CA certificate to the smt.crt file
- In the YaST2 CA management module change to the "Description" tab and select "Advanced / Export to File".
- Select "Only the Certificate in PEM Format" and enter "/srv/www/htdocs/smt.crt" as the filename.
- Select "Ok" to export the file.
- Leave YaST.
- Restart the smt server by entering "rcsmt restart" into the root shell. This will also restart the http server apache, so that apache uses the new certificate.
- Execute "clientSetup4SMT.sh --host smt-server.example.net" (adjust the FQDN to your SMT server) to import the new CA to the SMT clients and to make the clients to trust the new CA. On SLE 11 clients you can alternatively use the "yast2 inst_suse_register" module (select "Advanced" and follow the instructions).
- Execute "suse_register -L /root/.suse_register.log" to register the client against the SMT server.
Please find more documentation on Certificates in the SMT 11 documentation at http://www.novell.com/documentation/smt11/. In here see chapter 7.3, Server Certificates.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7006024
- Creation Date:18-MAY-10
- Modified Date:10-DEC-15
- SUSESubscription Management ToolSUSE Linux Enterprise Server
Did this document solve your problem? Provide Feedback