Bit new to all this stuff so please bear with me, I have been tasked with securing a website via SSL on one of our existing webservers. This particular web server has 1 public IP and runs 1 main website with 3 other ‘websites’ from within virtual directories. The firewall protected sites are accessed directly via the public IP together with the corresponding path to the virtual directory. My question is this, I know the CSR generation process stipulates either a netbios name / internal IP (for intranet) or external fqdn (for internet) in order to complete the request but is it possible to complete this process by specifying the current PUBLIC IP and generate an SSL thats valid for
OR do we HAVE to register this to a domain ?. The sites we current host arent really logically related so getting a domain to cover them all would be ultimately confusing for the end users.
Firstly thankyou very much for taking the time to reply, I basically did what you suggested in the first instance however I ran into a problem in actually generating the SSL cert via the 3month free trial facility. The online generator wouldnt let me enter a public IP to complete the SSL generation (it insisted on either internal IP or netbios name) which kind of threw me a little into thinking that I may need a different type of SSL cert to accomplish my task most cost effectively. Would using a netbios name / internal IP as opposed to an external IP to generate the SSL make any difference in terms of external accessibility to the site ?