- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- ProLiant SSL-gate (!)
Server Management - Remote Server Management
1754057
Members
2645
Online
108811
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
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
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
07-20-2010 05:12 AM
07-20-2010 05:12 AM
ProLiant SSL-gate (!)
After waiting for about 3 years, HP finally came with iLO FW 2.00. Promising!, maybe they changed the way SSL certificates are handled in iLO.
YESSSS!! The option FQDN appeared when requesting a SSL certificate.
But unfortunately, apparently the testing department has been sleeping during working hours…
Let me tell you the steps I’ve taken:
Upgrade to iLO FW2.00
Changed the ‘iLO 2 Subsystem Name’ to ‘ iLO-Server’
Changed the ‘Domain Name’ to ‘.domain.com’ (pay attention to the DOT as first character)
Restarted iLO.
Request certificate, copied request, put into the advanced certificate site of our own CA.
Issued the certificate (look promising, because the FQDN is really in the common name!)
Donwloaded the certnew.cer and edited with notepad, copied text and pasted into step 3.
OK! Certificate accepted! Please restart.
BUT after restarting, the default iLO certificate has become active! ARRGGGHHH
Did the same procedure but then with the option ‘Short Name’. This works as it has been working before!
But what is the point of having a certificate with only the short name ‘iLO-SERVER’ instead of ‘iLO-SERVER.domain.com????
Another thing:
When using our own CA, only 2003 CA works with self-signing SSL from iLO devices.
We tried to issue iLO certificates to a new Windows 2008 R2 with CA installed, but iLO cannot handle the output generated with CA 2008R2. It says:
X.509 Certificate Import Error
The Certificate could not be imported from the supplied X.509 Certificate data.
Check the following:
- Make sure that the input text was base64 encoded X.509 Certificate data.
- Make sure that the input X.509 Certificate data was intended for this server (not another server).
Concluding this: HP iLO department still did not manage to create a good SSL code!
Other whis-list:
Option to insert already purchased wildcard SSL.
I deeply hope someone of the iLO programming department is reading this, and hopefully they will put some effort in correctly programming a more then 3 year old pain in the ***.
Thank u for your time.
YESSSS!! The option FQDN appeared when requesting a SSL certificate.
But unfortunately, apparently the testing department has been sleeping during working hours…
Let me tell you the steps I’ve taken:
Upgrade to iLO FW2.00
Changed the ‘iLO 2 Subsystem Name’ to ‘ iLO-Server’
Changed the ‘Domain Name’ to ‘.domain.com’ (pay attention to the DOT as first character)
Restarted iLO.
Request certificate, copied request, put into the advanced certificate site of our own CA.
Issued the certificate (look promising, because the FQDN is really in the common name!)
Donwloaded the certnew.cer and edited with notepad, copied text and pasted into step 3.
OK! Certificate accepted! Please restart.
BUT after restarting, the default iLO certificate has become active! ARRGGGHHH
Did the same procedure but then with the option ‘Short Name’. This works as it has been working before!
But what is the point of having a certificate with only the short name ‘iLO-SERVER’ instead of ‘iLO-SERVER.domain.com????
Another thing:
When using our own CA, only 2003 CA works with self-signing SSL from iLO devices.
We tried to issue iLO certificates to a new Windows 2008 R2 with CA installed, but iLO cannot handle the output generated with CA 2008R2. It says:
X.509 Certificate Import Error
The Certificate could not be imported from the supplied X.509 Certificate data.
Check the following:
- Make sure that the input text was base64 encoded X.509 Certificate data.
- Make sure that the input X.509 Certificate data was intended for this server (not another server).
Concluding this: HP iLO department still did not manage to create a good SSL code!
Other whis-list:
Option to insert already purchased wildcard SSL.
I deeply hope someone of the iLO programming department is reading this, and hopefully they will put some effort in correctly programming a more then 3 year old pain in the ***.
Thank u for your time.
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