How to import a certificate into WorldClient
Purpose & Scope
WorldClient's web server currently does not support generating certificate requests. If you have IIS you can use its certificate wizard to create the request and import the response. WorldClient will then be able to use it. You do not need to continue to use IIS at that point, you can disable the service and continue to use WorldClient's built-in webserver.
If you have purchased or otherwise generated a certificate from some source other than MDaemon, you can still use that certificate by using the Microsoft Management Console (MMC) to import it into the certificate store that MDaemon uses.
- On your Windows toolbar, click Start -> Run., and then type 'mmc /a' into the 'Open:' text box.
- Click OK.
- In the Microsoft Management Console, click Console -> Add/Remove Snap-in. (or press Ctrl+M on your keyboard).
- On the Standalone tab, click Add.
- Click Certificates, and then click Add.
- Choose Computer account, and then click Next.
- Choose Local computer, and then click Finish.
- Click Close, and click OK.
- Under 'Certificates (Local Computer)', click the 'Certificates' subfolder under the 'Trusted Root Certification Authorities' folder if the certificate that you are importing is self-signed. If it is not self-signed then click the 'Personal' folder.
- Click Action -> All Tasks -> Import, and click Next.
- Enter the file path to the certificate that you wish to import (using the Browse button if necessary), and click Next.
- Click Next, and click Finish.
To verify the certificate will be visible to MDaemon, double click the certificate to view it from within the Certificates MMC. Verify that at the bottom of the General page is the text 'You have a private key that corresponds to this certificate.' On the Details page, look for the field 'Enhanced Key Usage' and verify it contains 'Server Authentication.' If those are missing, MDaemon will not be able to display the certificate.
Note: MDaemon will only display certificates that have private keys using the Personal Information Exchange format (PKCS #12). If your imported certificate does not appear in the list then you may need to import a *.PEM file, which contains both a certificate key and private key. Importing this file using the same process outlined above will convert it to the PKCS #12 format.
last updated 5-20-2009