- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- Why does ILO3 replace underscore characters in OU ...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
05-16-2016 01:19 AM
05-16-2016 01:19 AM
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.