<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ProLiant SSL-gate (!) in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/proliant-ssl-gate/m-p/4663575#M5124</link>
    <description>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.&lt;BR /&gt;YESSSS!! The option FQDN appeared when requesting a SSL certificate.&lt;BR /&gt;But unfortunately, apparently the testing department has been sleeping during working hours…&lt;BR /&gt;Let me tell you the steps I’ve taken:&lt;BR /&gt;Upgrade to iLO FW2.00&lt;BR /&gt;Changed the ‘iLO 2 Subsystem Name’ to ‘ iLO-Server’&lt;BR /&gt;Changed the ‘Domain Name’ to ‘.domain.com’ (pay attention to the DOT as first character)&lt;BR /&gt;Restarted iLO. &lt;BR /&gt;Request certificate, copied request, put into the advanced certificate site of our own CA. &lt;BR /&gt;Issued the certificate (look promising, because the FQDN is really in the common name!)&lt;BR /&gt;Donwloaded the certnew.cer and edited with notepad, copied text and pasted into step 3. &lt;BR /&gt;OK! Certificate accepted! Please restart. &lt;BR /&gt;BUT after restarting, the default iLO certificate has become active! ARRGGGHHH&lt;BR /&gt;&lt;BR /&gt;Did the same procedure but then with the option ‘Short Name’. This works as it has been working before! &lt;BR /&gt;But what is the point of having a certificate with only the short name ‘iLO-SERVER’ instead of ‘iLO-SERVER.domain.com???? &lt;BR /&gt;Another thing:&lt;BR /&gt;When using our own CA, only 2003 CA works with self-signing SSL from iLO devices.&lt;BR /&gt;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:&lt;BR /&gt;X.509 Certificate Import Error&lt;BR /&gt;The Certificate could not be imported from the supplied X.509 Certificate data.&lt;BR /&gt;&lt;BR /&gt;Check the following:&lt;BR /&gt;- Make sure that the input text was base64 encoded X.509 Certificate data.&lt;BR /&gt;- Make sure that the input X.509 Certificate data was intended for this server (not another server).&lt;BR /&gt;&lt;BR /&gt;Concluding this: HP iLO department still did not manage to create a good SSL code!&lt;BR /&gt;Other whis-list:&lt;BR /&gt;Option to insert already purchased wildcard SSL.&lt;BR /&gt;&lt;BR /&gt;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 ***.&lt;BR /&gt;&lt;BR /&gt;Thank u for your time.</description>
    <pubDate>Tue, 20 Jul 2010 12:12:16 GMT</pubDate>
    <dc:creator>Gerrit Heinen - T-ICT B</dc:creator>
    <dc:date>2010-07-20T12:12:16Z</dc:date>
    <item>
      <title>ProLiant SSL-gate (!)</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/proliant-ssl-gate/m-p/4663575#M5124</link>
      <description>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.&lt;BR /&gt;YESSSS!! The option FQDN appeared when requesting a SSL certificate.&lt;BR /&gt;But unfortunately, apparently the testing department has been sleeping during working hours…&lt;BR /&gt;Let me tell you the steps I’ve taken:&lt;BR /&gt;Upgrade to iLO FW2.00&lt;BR /&gt;Changed the ‘iLO 2 Subsystem Name’ to ‘ iLO-Server’&lt;BR /&gt;Changed the ‘Domain Name’ to ‘.domain.com’ (pay attention to the DOT as first character)&lt;BR /&gt;Restarted iLO. &lt;BR /&gt;Request certificate, copied request, put into the advanced certificate site of our own CA. &lt;BR /&gt;Issued the certificate (look promising, because the FQDN is really in the common name!)&lt;BR /&gt;Donwloaded the certnew.cer and edited with notepad, copied text and pasted into step 3. &lt;BR /&gt;OK! Certificate accepted! Please restart. &lt;BR /&gt;BUT after restarting, the default iLO certificate has become active! ARRGGGHHH&lt;BR /&gt;&lt;BR /&gt;Did the same procedure but then with the option ‘Short Name’. This works as it has been working before! &lt;BR /&gt;But what is the point of having a certificate with only the short name ‘iLO-SERVER’ instead of ‘iLO-SERVER.domain.com???? &lt;BR /&gt;Another thing:&lt;BR /&gt;When using our own CA, only 2003 CA works with self-signing SSL from iLO devices.&lt;BR /&gt;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:&lt;BR /&gt;X.509 Certificate Import Error&lt;BR /&gt;The Certificate could not be imported from the supplied X.509 Certificate data.&lt;BR /&gt;&lt;BR /&gt;Check the following:&lt;BR /&gt;- Make sure that the input text was base64 encoded X.509 Certificate data.&lt;BR /&gt;- Make sure that the input X.509 Certificate data was intended for this server (not another server).&lt;BR /&gt;&lt;BR /&gt;Concluding this: HP iLO department still did not manage to create a good SSL code!&lt;BR /&gt;Other whis-list:&lt;BR /&gt;Option to insert already purchased wildcard SSL.&lt;BR /&gt;&lt;BR /&gt;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 ***.&lt;BR /&gt;&lt;BR /&gt;Thank u for your time.</description>
      <pubDate>Tue, 20 Jul 2010 12:12:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/proliant-ssl-gate/m-p/4663575#M5124</guid>
      <dc:creator>Gerrit Heinen - T-ICT B</dc:creator>
      <dc:date>2010-07-20T12:12:16Z</dc:date>
    </item>
  </channel>
</rss>

