diff --git a/src/site/xdoc/sslsetup.xml b/src/site/xdoc/sslsetup.xml index 47c88751..1a75f6e9 100644 --- a/src/site/xdoc/sslsetup.xml +++ b/src/site/xdoc/sslsetup.xml @@ -53,12 +53,50 @@ davmail.ssl.keystorePass=password]]>

In most cases, using https in OWA url is enough to secure communication between DavMail and Exchange. However, with Exchange servers setup to require mutual authentication, you will have to register - client certificate in DavMail settings, either through PKCS11 (smartcard) or file certificate: + your client certificate in DavMail settings, either through PKCS11 (smartcard) or file certificate.

+

To use a client certificate provided as a PKCS12 file, set the following keys in DavMail:

+

For a smartcard, first make sure you PKCS11 module is correctly installed by testing mutual + authentication through a browser. Then set the following properties in DavMail:

+ +

PKCS11 library is the full path to the PKCS11 module (.so on Unix, .dll on windows) or simple + library name if PATH (Windows) or LD_LIBRARY_PATH (Unix) already contains the full path. Add any + additional PKCS11 parameter in PKCS11 Config parameter, e.g. slot = 2. +

+

To adjust your settings, you can try to access the smartcard with java keytool. First create a file + named pkcs11.config with the following lines:

+ +

and list certificates with keytool:

+ keytool -keystore NONE -storetype PKCS11 -providerClass sun.security.pkcs11.SunPKCS11 -providerArg pkcs11.config -list -v + +

Sample pkcs11.config for NSS Soft token (Thunderbird/Firefox):

+ + +

Another one for Coolkey (see Coolkey for Debian + and United States Department of Defense Common Access Cards):

+ + +

More details on java PKCS11 setup in + Sun PKCS11 guide +

+