The server that this is for will operate in a intranet environment...I have Apache working with SSL.  I am using a self-signed SSL Certificate created using the steps outlined here: http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#realcertunder the How do I create and use my own Certificate Authority (CA) section.  When I create the certificate, I use the domain in CommonName field so when I access https://mysite.com after installing the certificate in the web browser, everything is smooth...  When I try to use the server by IP address, I receive the following type of error (IE) even though my certificate for the domain name is already installed in the web browser:I would like the site to be accessible by IP address too without having the web browser have a fit (https://1.2.3.4).  Is it possible to have a setup where using the IP address of the server or domain for https will work???  I need this setup because some people access the server by IP and some use the domain name.  UPDATE: I Tried using 'Subject Alternative Names' and it worked great, but this feature is due to expire Nov. 1, 2015...So, DON'T USE IT!!!.  Here is some follow up documentation on the subject:https://www.digicert.com/internal-names.htmhttps://cabforum.org/wp-content/uploads/Guidance-Deprecated-Internal-Names.pdfHere is a 'blurb' from the above .pdf on the subject:Also as of the Effective Date, the CA SHALL NOT issue a certificate with an Expiry Date later than 1 November 2015 with a SAN or Subject Common Name field containing a Reserved IP Address or Internal Server Name. Bummer, had it all working great but ran into this brick wall after creating a certificate that is good for 10 yrs and seeing that the web browsers wouldn't except it.  Anyhow, looking for a work-a-round if there is one...
SSL by IP or domain
centos;apache httpd;openssl;certificates