HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Server Management - Remote Server Management
cancel
Showing results for 
Search instead for 
Did you mean: 

Why does ILO3 replace underscore characters in OU field with spaces when a CSR is generated?

 
skgb
Occasional Contributor

Why does ILO3 replace underscore characters in OU field with spaces when a CSR is generated?

Hope someone can help with this.

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.

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?

Here is one link:

https://support.rackspace.com/how-to/generate-a-csr-with-openssl/

showing that underscore is not a forbidden character in OU fields.

Alternatively, is there an "escape sequence" that should be used to prefix/surround the underscore so that it is accepted?

 

This does not happen on ILO4 systems, btw.

---

 

Regards,

Richard.