Security - Local Server Certificate

The Local Server Certificate link enables you to use certificates that are not generated by HP.

If you use the following process, the self-signed certificate that was originally generated by the HP System Management Homepage (HP SMH) is replaced with one that was issued by a certificate authority (CA).

The first step of the process is to cause the HP SMH to create a Certificate Request (PKCS #10). This request uses the original private key that was associated with the self-signed certificate and generates the appropriate data for certificate request. The private key never leaves the server during this process.
After the PKCS #10 data has been created, the next step is to send it to a certificate authority. Follow your company policy with regard to sending secure requests for and receiving secure certificates.
After the certificate authority has returned PKCS #7 data, the final step is to import this into HP SMH.
After the PKCS #7 data has been successfully imported, the original \hp\sslshare\cert.pem certificate file for Windows, and the /opt/hpsmh/sslshare/cert.pem file for HP-UX and Linux is overwritten with the system certificate from that PKCS #7 data envelope. The same private key is used for the new imported certificate as was used with the previous self-signed certificate. This private key is randomly generated at startup when no key file exists.

Select SettingsSystem Management HomepageSecurity.
Select Local Server Certificate.
Optionally, you can replace the default values in the Organization and/or Organizational Unit fields with your own values up to a maximum of 64 characters.
Click [Create PKCS #10 Data]. A screen appears indicating that the PKCS #10 Certificate Request data has been successfully generated and stored in /opt/hpsmh/sslshare/req_cr.pem for HP-UX, /opt/hp/sslshare/req_cr.pem for Linux, and c:\hp\sslshare\req_cr.pem for Windows.
Copy the certificate data.
Use a secure method to send PKCS #10 certificate request data to a certificate authority and request the certificate request reply data in the form of PKCS #7 format. Request that the reply data be in Base64 encoded format. If your organization has its own Public-key infrastructure (PKI) or Certificate Server implemented, send the PKCS #10 data to the CA manager and request the PKCS #7 reply data.
Note:
A third-party certificate signer generally charges a fee.
When the certificate signer sends the PKCS #7 encoded certificate request reply data to you, copy the data from the PKCS #7 certificate request reply and paste the copied data in the PKCS #7 Data field. In this case, skip the next step.
Click [Import PKCS #7 Data]. A message appears indicating whether the customer-generated certificate was successfully imported.
Restart HP SMH.
Browse to the managed system that contains the imported certificate.

Select to view the certificate when prompted by the browser. Be sure the signer is listed as the signer you used, and not HP, before importing the certificate into your browser.


Note:


	If the certificate signer of your choice sends you a certificate file in Base64 encoded form instead of PKCS #7 data, copy the Base64 encoded certificate file to `/opt/hpsmh/sslshare/req_cr.pem` for HP-UX, `/opt/hp/sslshare/req_cr.pem` for Linux, and `c:\hp\sslshare\req_cr.pem` for Windows; then restart HP SMH.

HP System Management Homepage

Local Server Certificate

Related Topics