Recently I needed to get SSL up and running on some internal development and test environments. We know as the cert hasn’t come from a trusted source the client will recieve certificate errors – not a problem internally.
Reading round the web the tool to use is SSLDiag (which also has a 64 bit version).
Get it here:
Here’s my notes on running the app to get the cert in the dev environment.
You’ll need to get the ID of the website from IIS, the default site has an ID of ’1′ but other sites usually have a 9 character ID.
Consider using a VBS script or similar to enumerate your websites and get the ID, such as the VBS here: http://blogs.msdn.com/b/david.wang/archive/2006/06/08/howto-enumerate-iis-website-and-ftpsite-configuration-vbscript-using-adsi.aspx
Here’s the command line arguements:
C:\Program Files\IIS Resources\SSLDiag>ssldiag /selfssl /N:CN={SITEURL} /V:{DAYSTILLEXPIRE} /S:{IISSITEID}
I.E.
C:\Program Files\IIS Resources\SSLDiag>ssldiag /selfssl /N:CN=dev.mysite.co.uk /V:3650 /S:777555888
–After this is ran you need to add the IP and SSL port.
1. Open iis manager
2. Open properties for website
3. Click ‘Advanced’ at then of IP address dropdown
4. Add IP and 443 to the bottom half of the dialog






