<tr><th><ahref="directive-dict.html#Compatibility">Compatibility:</a></th><td><var>certid</var> available in 2.5.1 and later.</td></tr>
</table>
<p>
This directive points to a file with certificate data in PEM format.
At a minimum, the file must include an end-entity (leaf) certificate.
This directive points to a file with certificate data in PEM format, or the certificate identifier through a configured cryptographic token.
If using a PEM file, at minimum, the file must include an end-entity (leaf) certificate.
The directive can be used multiple times (referencing different filenames)
to support multiple algorithms for server authentication - typically
RSA, DSA, and ECC. The number of supported algorithms depends on the
@@ -660,6 +661,14 @@ after the certificates using a separate key file. If the private
key is encrypted, the pass phrase dialog is forced at startup time.
</p>
<p>As an alternative to storing certificates and private keys in
files, a certificate identifier can be used to identify a certificate
stored in a token. Currently, only <ahref="https://tools.ietf.org/html/rfc7512">PKCS#11 URIs</a> are
recognized as certificate identifiers, and can be used in conjunction
with the OpenSSL <code>pkcs11</code> engine configured with <codeclass="directive"><ahref="#sslcryptodevice">SSLCryptoDevice</a></code>. If <codeclass="directive"><ahref="#sslcertificatekeyfile">SSLCertificateKeyFile</a></code> is omitted, the
certificate and private key can be loaded through the single
identifier specified with <codeclass="directive"><ahref="#sslcertificatefile">SSLCertificateFile</a></code>.</p>
<divclass="note">
<h3>DH parameter interoperability with primes > 1024 bit</h3>
<p>
@@ -703,7 +712,12 @@ thus using a custom/suitable length.
Changes for docs/manual/mod/quickreference.html.en: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -1081,7 +1081,7 @@ Client Auth</td></tr>
<trclass="odd"><td><ahref="mod_ssl.html#sslcarevocationpath">SSLCARevocationPath <em>directory-path</em></a></td><td></td><td>sv</td><td>E</td></tr><trclass="odd"><tdclass="descr"colspan="4">Directory of PEM-encoded CA CRLs for
Client Auth</td></tr>
<tr><td><ahref="mod_ssl.html#sslcertificatechainfile">SSLCertificateChainFile <var>file-path</var></a></td><td></td><td>sv</td><td>E</td></tr><tr><tdclass="descr"colspan="4">File of PEM-encoded Server CA Certificates</td></tr>
<trclass="odd"><td><ahref="mod_ssl.html#sslcertificatefile">SSLCertificateFile <var>file-path</var></a></td><td></td><td>sv</td><td>E</td></tr><trclass="odd"><tdclass="descr"colspan="4">Server PEM-encoded X.509 certificate data file</td></tr>
<trclass="odd"><td><ahref="mod_ssl.html#sslcertificatefile">SSLCertificateFile <var>file-path</var>|<var>certid</var></a></td><td></td><td>sv</td><td>E</td></tr><trclass="odd"><tdclass="descr"colspan="4">Server PEM-encoded X.509 certificate data file or token identifier</td></tr>
<trclass="odd"><td><ahref="mod_ssl.html#sslciphersuite">SSLCipherSuite [<em>protocol</em>] <em>cipher-spec</em></a></td><td> DEFAULT (depends on +</td><td>svdh</td><td>E</td></tr><trclass="odd"><tdclass="descr"colspan="4">Cipher Suite available for negotiation in SSL