From 8391c6f3fe27e58aee67a1863284ab160ab430e9 Mon Sep 17 00:00:00 2001
From: Daniel Baumann
This directive sets the all-in-one file where you keep the certificates and @@ -1905,13 +1906,10 @@ keys used for authentication of the proxy server to remote servers.
This referenced file is simply the concatenation of the various
PEM-encoded certificate files. Use this directive alternatively or
-additionally to SSLProxyMachineCertificatePath
. The
-referenced file can contain any number of pairs of client certificate
-and associated private key. Each pair can be specified in either
-(certificate, key) or (key, certificate) order. If the file includes
-any non-leaf certificate, or any unmatched key and certificate pair, a
-configuration error will be issued at startup.
-
SSLProxyMachineCertificatePath
. The referenced file can contain any number of pairs of client
+certificate and associated private key. Each pair can be specified in
+either (certificate, key) or (key, certificate) order. Non-leaf (CA) certificates can
+also be included in the file, and are treated as if configured with SSLProxyMachineCertificateChainFile
.
When challenged to provide a client certificate by a remote server,
the server should provide a list of acceptable certificate
@@ -1922,7 +1920,7 @@ client cert/key. If a list of CA names is provided,
to find a configured client cert which was issued either directly by
that CA, or indirectly via any number of intermediary CA certificates.
The chain of intermediate CA certificates can be built from those
-configured with SSLProxyMachineCertificateChainFile
. The
+included in the file, or configured with SSLProxyMachineCertificateChainFile
. The
first configured matching certificate will then be supplied in
response to the challenge.