Article ID: 2582, created on Oct 29, 2007, last review on May 9, 2014

  • Applies to:
  • Pro Control Panel Windows

AdditionalInformation

View Knowledge
Knowledge ID 1750
Product : EnsimPro for Windows 2000
Version : 3.6
Topic : FAQ

Title
Exporting SSL certificates from IIS to secure tunnel using Openssl.

Summary
Exporting SSL certificates from IIS to secure tunnel using Openssl.

Prevention


Details

Follow the following steps to export SSL certificate from IIS to secure tunnel using Openssl:

1) First install the certificate in the local store using certificate manager. 

2) If you have to use it for IIS then please see to it that it appears in the personal store under the local computer.

3) Export the certificate in pkcs12 format on your C drive. Please see to it that the private keys are also exported.

4) Go to command prompt and then do the following

C:\Program Files\Ensim\Webppliance\stunnel\w2k>openssl pkcs12 -nodes -in c:\pkcs.pfx -info -out stunell1.pem

Where pkcs.pfx in the exported certificate and stunell1.pem is the certificate the stunnel will use. When you run this command then it will ask you for the password please provide the password that you gave while exporting the certificate. It will save the file. 

5) Backup the C:\Program Files\Ensim\Sitedata\webppliance\conf\ssl\ssl.pem by some other name say stunnel.pem.org.

6) Copy the stunell1.pem that was created by you using openssl in the same directory and rename it to stunnel.pem

7) Restart the Virtualhosting service. 

Now when you view the certificate you will find that your certificate is being served.

Note: Please note that in this process we have disabled des and 3des protection as during the import if you enable it then on starting the stunnel process it actually prompts you for the password. Since the service runs in background mode it will not start due to the above condition.


Attachments


Related Knowledge

Related Links
 
Last ModifiedUsageSatisfiedLast Used
8/20/2004 10:53:53 AM26 10/11/2007 4:54:08 AM

8e19bcddff0cc55cafe80c841132ca59 3ccb419cf98083f3bb45808fba8dbc7c 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF