- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- SSL certificate request with FQDN
Server Management - Remote Server Management
1753681
Members
6004
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-23-2009 01:56 AM
12-23-2009 01:56 AM
SSL certificate request with FQDN
Hello all,
I have a brand new DL380 G6 with iLO2 and I am trying to sign the SSL certificate of the server with our local CA certificate.
The problem is that the certificate request generated by the iLO contains DN with only the hostname and not the domain name (my server is called g6test and domain is monitor).
I always get this:
Subject: C=US, ST=Texas, L=Houston, O=Hewlett-Packard Development Company, OU=ISS, CN=g6test
but I need this:
Subject: C=US, ST=Texas, L=Houston, O=Hewlett-Packard Development Company, OU=ISS, CN=g6test.monitor
because otherwise the browser complains about difference between names.
The other option would be to upload both key and crt to the iLO, but I don't know if it is possible.
Thank you very much for any help.
I have a brand new DL380 G6 with iLO2 and I am trying to sign the SSL certificate of the server with our local CA certificate.
The problem is that the certificate request generated by the iLO contains DN with only the hostname and not the domain name (my server is called g6test and domain is monitor).
I always get this:
Subject: C=US, ST=Texas, L=Houston, O=Hewlett-Packard Development Company, OU=ISS, CN=g6test
but I need this:
Subject: C=US, ST=Texas, L=Houston, O=Hewlett-Packard Development Company, OU=ISS, CN=g6test.monitor
because otherwise the browser complains about difference between names.
The other option would be to upload both key and crt to the iLO, but I don't know if it is possible.
Thank you very much for any help.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2010 09:35 AM
01-07-2010 09:35 AM
Re: SSL certificate request with FQDN
Look at the thread "No dots in iLO2 name"
My quick fix (quoted from that thread) was to turn off JavaScript.
"There's a simple workaround iff you're willing to use the web interface.
A very common mistake in Web programming is to rely exclusively on JavaScript for input sanity checking. One of the basic things we do when testing web site code is to see whether the errors trapped by JavaScript are trapped when the form is submitted regardless; good code on the server side will catch the same errors and will reject the submission, although it probably has to be handled differently.
Occasionally, we'll run across something really strange such as the CSR issue mentioned above. Since we use a local CA and root cert, we really like to be able to install a cert we issue. It was a pretty obvious thing to try turning off JavaScript, since it was a JS error popping up. Appears to work just fine if you do that. Turn it back on after you submit the form and leave the page."
My quick fix (quoted from that thread) was to turn off JavaScript.
"There's a simple workaround iff you're willing to use the web interface.
A very common mistake in Web programming is to rely exclusively on JavaScript for input sanity checking. One of the basic things we do when testing web site code is to see whether the errors trapped by JavaScript are trapped when the form is submitted regardless; good code on the server side will catch the same errors and will reject the submission, although it probably has to be handled differently.
Occasionally, we'll run across something really strange such as the CSR issue mentioned above. Since we use a local CA and root cert, we really like to be able to install a cert we issue. It was a pretty obvious thing to try turning off JavaScript, since it was a JS error popping up. Appears to work just fine if you do that. Turn it back on after you submit the form and leave the page."
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP