Accessing an SSL-Enabled Server from a Browser or WebDAV Client
When you create a certificate template and set it in your app server, MarkLogic Server automatically generates a temporary self-signed MarkLogic Server certificate authority that signs host certificates. If you have not yet received a signed certificate for your SSL-enabled app server from a certificate authority, your browser must accept the temporary self-signed certificate authority before it can access the app server. There are two alternative ways to do this, both of which are browser-dependent and described below.
To enable WebDAV clients to access an SSL-enabled app server, you must follow the procedure described in Importing a Self-Signed Certificate Authority into Windows.
To enable a single browser to access the SSL-enabled app server, you can create a security exception for the self-signed certificate in your browser, as described in the following sections:
If you need to enable a number of browsers to access the SSL-enabled app server, you might want each browser to import the self-signed certificate authority for the certificate template. Once this is done, all certificates signed by the certificate authority will be trusted by the browser, so you can distribute new certificates without requiring each browser to create new security exceptions. The following sections describe how to import the self-signed MarkLogic Server certificate authority: