<?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 Why does ILO3 replace underscore characters in OU field with spaces when a CSR is generated? in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/why-does-ilo3-replace-underscore-characters-in-ou-field-with/m-p/6859573#M7770</link>
    <description>&lt;P&gt;Hope someone can help with this.&lt;/P&gt;&lt;P&gt;On an ILO3 system (running firmware version 1.87), if we generate a CSR whose OU field contains an underscore character, the underscore character is *silently* transformed to a space character. As the content of the OU field has to be validated against a known list when the CSR is submitted for approval, the validation fails and hence no cert is issued which is a show-stopper for us.&lt;/P&gt;&lt;P&gt;If there is some good technical reason for the non-acceptance of underscore characters, then the GUI panel for filling out the CSR/cert fields should issue a warning at that stage., surely?&lt;/P&gt;&lt;P&gt;Here is one link:&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.rackspace.com/how-to/generate-a-csr-with-openssl/" target="_blank"&gt;https://support.rackspace.com/how-to/generate-a-csr-with-openssl/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;showing that underscore is not a forbidden character in OU fields.&lt;/P&gt;&lt;P&gt;Alternatively, is there an "escape sequence" that should be used to prefix/surround the underscore so that it is accepted?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This does not happen on ILO4 systems, btw.&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Richard.&lt;/P&gt;</description>
    <pubDate>Mon, 16 May 2016 08:19:17 GMT</pubDate>
    <dc:creator>skgb</dc:creator>
    <dc:date>2016-05-16T08:19:17Z</dc:date>
    <item>
      <title>Why does ILO3 replace underscore characters in OU field with spaces when a CSR is generated?</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/why-does-ilo3-replace-underscore-characters-in-ou-field-with/m-p/6859573#M7770</link>
      <description>&lt;P&gt;Hope someone can help with this.&lt;/P&gt;&lt;P&gt;On an ILO3 system (running firmware version 1.87), if we generate a CSR whose OU field contains an underscore character, the underscore character is *silently* transformed to a space character. As the content of the OU field has to be validated against a known list when the CSR is submitted for approval, the validation fails and hence no cert is issued which is a show-stopper for us.&lt;/P&gt;&lt;P&gt;If there is some good technical reason for the non-acceptance of underscore characters, then the GUI panel for filling out the CSR/cert fields should issue a warning at that stage., surely?&lt;/P&gt;&lt;P&gt;Here is one link:&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.rackspace.com/how-to/generate-a-csr-with-openssl/" target="_blank"&gt;https://support.rackspace.com/how-to/generate-a-csr-with-openssl/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;showing that underscore is not a forbidden character in OU fields.&lt;/P&gt;&lt;P&gt;Alternatively, is there an "escape sequence" that should be used to prefix/surround the underscore so that it is accepted?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This does not happen on ILO4 systems, btw.&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Richard.&lt;/P&gt;</description>
      <pubDate>Mon, 16 May 2016 08:19:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/why-does-ilo3-replace-underscore-characters-in-ou-field-with/m-p/6859573#M7770</guid>
      <dc:creator>skgb</dc:creator>
      <dc:date>2016-05-16T08:19:17Z</dc:date>
    </item>
  </channel>
</rss>

