Maintenance Tasks
468
Titan SiliconServer
2.
Prompts will appear, requesting details of the following: (Hit
enter
to accept the default
values.)
Organizational Unit (OU)
Organization (O)
Location (L)
State (ST)
Country (C)
Valid Period (in days)
Key Size (e.g. 1024, 2048 – must be divisible by 64).
3.
After confirming the input, a new private key and self-signed certificate will be generated.
4.
Restart the web server (tomcat) when prompted so that it may pick up the new SSL
certificate.
5.
Close and restart any browsers used to connect to the SMU. This is required to purge the
browser of any previously negotiated SSL session values.
When logging into the SMU Web UI, the new SSL Certificate should be provided.
6.
Now propagate the new SSL certificate to all managed servers.
Go to Home > SMU Administration > Managed SiliconServers.
For each server, click "details" and then "OK".
A backup of this private key and certificate (i.e. the whole keystore) may be made for
safekeeping.
1.
Log onto the Web UI.
2.
Go to Home > SMU Administration > SMU Backup
3.
Click "backup" and save the resulting zip file to safe and secure location.
The zip file contains a full backup of the SMU’s configuration information. The file
"smu.keystore" within the zip file contains the SMU’s private key.
Generating a Certificate Signing Request (CSR)
A Certificate Signing Request is a file that contains the encoded information needed to request a
certificate from an authority. After generating the Certificate Signing Request, it can be
submitted to the authority. For example, on Verisign’s Web site at
http://www.verisign.com/
,
paste the Certificate Signing Request into the Web page.
To generate a CSR
1.
Log onto the SMU (through ssh or through its serial port) as the user manager, then
type:
sudo cert-gencsr.sh
Enter the manager user’s password when prompted.
