<?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 Re: iLO certification in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/ilo-certification/m-p/4271733#M3890</link>
    <description>hi&lt;BR /&gt;&lt;BR /&gt;to be hopefully heard I think you must call HP&lt;BR /&gt;that's the only way to get some answers&lt;BR /&gt;&lt;BR /&gt;I am almost sure no one related with "ilo high features" will read this in his entire life almost sure about it</description>
    <pubDate>Fri, 19 Sep 2008 04:01:48 GMT</pubDate>
    <dc:creator>KarloChacon</dc:creator>
    <dc:date>2008-09-19T04:01:48Z</dc:date>
    <item>
      <title>iLO certification</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ilo-certification/m-p/4271732#M3889</link>
      <description>As some of u know, there is an issue with the FQDN for SSL on iLO devices.&lt;BR /&gt;When requesting a certificate on iLO, the request ONLY contains the hostname and NOT the FQDN.&lt;BR /&gt;After emailing with HP Support, the technician came with the following answer:&lt;BR /&gt;"ILO certificate request is only using the host name .ILO certification creation request doesnt go using the FQDN of the ILO and it is working as designed."&lt;BR /&gt;&lt;BR /&gt;Correct me if i'm wrong, if I (or someone else) wants to make use of SSL on the correct way, it MUST have a FQDN SSL cert.&lt;BR /&gt;&lt;BR /&gt;I have my own CA provider and want to connect to an iLO on the internet through https://FQDN:portnumber. But it seems impossible because of the 'design' of iLO.&lt;BR /&gt;&lt;BR /&gt;Hopefully a technician reeds this, and speaks to the people responsible for iLO. &lt;BR /&gt;Because this is a feature that completes iLO. It is a wonderfull product, but this missing feature is really bugging me!&lt;BR /&gt;&lt;BR /&gt;If other people have the same Issue, please post a reply. The more interest, the more likely it will be fixed with a new release of the iLO firmware.&lt;BR /&gt;&lt;BR /&gt;Thank u for your time!</description>
      <pubDate>Thu, 18 Sep 2008 06:44:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ilo-certification/m-p/4271732#M3889</guid>
      <dc:creator>Gerrit Heinen</dc:creator>
      <dc:date>2008-09-18T06:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: iLO certification</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ilo-certification/m-p/4271733#M3890</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;to be hopefully heard I think you must call HP&lt;BR /&gt;that's the only way to get some answers&lt;BR /&gt;&lt;BR /&gt;I am almost sure no one related with "ilo high features" will read this in his entire life almost sure about it</description>
      <pubDate>Fri, 19 Sep 2008 04:01:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ilo-certification/m-p/4271733#M3890</guid>
      <dc:creator>KarloChacon</dc:creator>
      <dc:date>2008-09-19T04:01:48Z</dc:date>
    </item>
    <item>
      <title>Re: iLO certification</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ilo-certification/m-p/4271734#M3891</link>
      <description>HP is investigating a means to allow iLO to generate certificate signing requests (CSRs) using the FQDN, however this is not guaranteed or promised.  At this time, the HP support response is correct.</description>
      <pubDate>Fri, 19 Sep 2008 18:18:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ilo-certification/m-p/4271734#M3891</guid>
      <dc:creator>acartes</dc:creator>
      <dc:date>2008-09-19T18:18:17Z</dc:date>
    </item>
  </channel>
</rss>

