I'm currently researching how to implement SSL connections through Google's PageSpeed Service. I have been accepted into the program; but I'm having issues conceptualizing how SSL connections will work.
I am using IIS 7, and have production certificates already for multiple domains. Google states you can add up to 50 domains... but did not specify how many could utilize SSL.
Will all of my domains be able to serve SSL connections with Google PageSpeed?
Do I need new SSL certificates?
If not, do I upload the private or public part of the certificate to Google?
How do I get these keys out of IIS?
Do any certificates from Google need to be installed on my server?
The SSL guide offers little in the way of hand-holding.
https:/
I'm hoping someone out there has gone through this before and can guide me.
As I said before, we have several domains; and I was planning on using one of the less trafficked sites for SSL testing. I don't want to lock myself out from having the ability to add the more important domains I manage.
Thanks.
-----------------------------------
I need some hand holding with the setup of SSL support for Google PageSpeed Service. The accepted answer will outline the steps needed to setup multiple IIS sites with Google PageSpeed Service, all of which will utilize SSL. The current sites each have their own SSL certificate (not self-signed). The accepted answer will also outline how Google implements the SSL proxying.
-----------------------------------
Using MMC I can extract the current certificate out of the Certificates snap-in. Then convert the .pfx with openssl.
openssl pkcs12 -in certificate.pfx -out unencrypted.pem -nodes
Both the private key, and the certificate (contains public key) need to be uploaded to Google per their documentation