Hello all,
I have been trying to setup a SSL website for development purposes. I'd like to be able to view the page without all the certificate errors! Ok, so I just went back and removed the certificate, so that I will be starting from scratch. Hopefully, with some help from all you fine people over here at: IIS. :-)
Ok, so some important infromation:
The security certificate for this website does not come from a trusted source. The security certificate for this website was issued for a different website's address.
I was able to deal with the certificate not coming from a trusted source. However, during the install process, I did receive the "Security Warning" dialog box that states:
You are about to install a certificate from a certification authority (CA) claiming to represent: The public ip address for the SSL site ":" and portnumber Windows cannot validate that the certificate is actually from "https://IpAddress:PortNumber/". You should confirm its origin by contacting "https://IpAddress:PortNumber/". The following number will assist you in this process: Thumprint ():;alkjdl;kfjal;sjkdl;kjfaskl;jdkl;jakl;jfdkl;sjskl;a Warning: If you install this root certificate, Windows will automatically trust any certificate issued ... blah, blah blah ... you accept this risk
So, this obviously has to do with the Certficate Name, Right?!
My server is behind a router. I do not plan on registering a Domain Name through a registrar just for development purposes. Originally, when I created the self-signed certificate, I used the exact IP address and port number as the argument for /N:CN= .... I was unsure if that value would accept intergers, but apparently it does because the certificate was created. Also, I could just accept the risks when installing the certificate to the client machine. When I went to the website, I'd still get the error about the certificate being issued for a different website's address that there was no way to validate whether it was coming from the correct source.
I typed this exactly: selfssl.exe /T /N:CN=https://IPAddress:PortNumber ... where ip address is actually the public IP address of my router. I just realized that could be what was causing the issue. I certianly do not want to use the IP address of the server on the local network. Anyway, even if I did, I tried that too. lol
If someone would be so kind as to inform me on how to overcome this issue, I can't even begin to express to you how very appreciative I will be.
Thanks for reading my post! :-)