- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: SMH self-signed certificate
Server Management - Systems Insight Manager
1752782
Members
6257
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2010 04:03 AM
тАО10-20-2010 04:03 AM
SMH self-signed certificate
Recent scans indicated certificate errors (hostname mismatch) for SMH. The built-in CSR mechanism (Settings-->SMH-->Security-->Local Server Certificate) is not very flexible and I had a hard time getting the FQDN in the request. Additionally, HP documentation indicates that if HP SIM is installed after HP SMH is installed, the HP SMH 2048-bit key pair is replaced with the HP SIM 1024-bit key pair, so a CSR on my machine would be using a 1024 bit key.
It is difficult to find documentation about the local server certificate online, but I have found that on Windows, the SMH certificate is located at c:\hp\sslshare\cert.pem and the private key is located at c:\hp\sslshare\file.pem.
I decided to try replacing these files to get the certificate I wanted. I installed OpenSSL on a workstation and ran the following command:
openssl req -new -newkey rsa:2048 -nodes -subj /CN=/O=/OU=/C=/ST=/L= -keyout mykey.pem -out myreq.pem
I renamed the resulting mykey.pem to file.pem and replaced the existing file on the server. I used myreq.pem to generate a certificate on our local CA. I renamed the resulting certificate file cert.pem and replaced the existing file on the server. After restarting the HP Systems Management Homepage service on the server, SMH starting using the new certificate.
I am pretty new to managing certificates, so I am wondering - does this all seem right. Though I haven't noticed any degredation, did I break something else by replacing these files? Am I as secure as I was with the auto-genterated, self-signed certificate?
It is difficult to find documentation about the local server certificate online, but I have found that on Windows, the SMH certificate is located at c:\hp\sslshare\cert.pem and the private key is located at c:\hp\sslshare\file.pem.
I decided to try replacing these files to get the certificate I wanted. I installed OpenSSL on a workstation and ran the following command:
openssl req -new -newkey rsa:2048 -nodes -subj /CN=
I renamed the resulting mykey.pem to file.pem and replaced the existing file on the server. I used myreq.pem to generate a certificate on our local CA. I renamed the resulting certificate file cert.pem and replaced the existing file on the server. After restarting the HP Systems Management Homepage service on the server, SMH starting using the new certificate.
I am pretty new to managing certificates, so I am wondering - does this all seem right. Though I haven't noticed any degredation, did I break something else by replacing these files? Am I as secure as I was with the auto-genterated, self-signed certificate?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2010 12:01 AM
тАО10-28-2010 12:01 AM
Re: SMH self-signed certificate
Though the given scenario seems to be unsupported by the software, but I think, you can verify the changes by trying to open all available webapps, in your setup.
And, also you are as secured as with the original configuration.
Thanks.
And, also you are as secured as with the original configuration.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2010 03:56 AM
тАО10-28-2010 03:56 AM
Re: SMH self-signed certificate
This procedure may have broken the vcrepository. See: http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1453419
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP