
Chapter 4: Configuring the High-Level Network
4-98
To insert a cipher specification from the command line
Specify the cipher insert argument with the bigpipe proxy command, as
follows:
b proxy <ip>:<service> [clientssl] cipher insert <enable | disable>
Client certificate fields
When adding an SSL proxy, you can configure the proxy to insert into an
HTTP request a header for each field of a client certificate. This feature is
most useful when:
• You have configured the SSL proxy to authenticate clients with the
request option. For more information, see Configuring client-side
authentication, on page 4-93.
• You want to better control the load balancing of your network traffic. In
this case, you can create a rule that performs load balancing according to
the certificate information in the header. Figure 4.46 shows an example.
Table 4.18 shows the client certificate headers that the SSL proxy can insert
into a client request. For each header, the required format, description, and
keyword is shown.
if (exists http_header "SSLClientCertStatus") {
if (http_header "SSLClientCertStatus" contains "OK") {
use ( authenticated_pool )
}
else {
redirect to "<https://%h/authenticationfailed.html>"
}
}
else {
redirect to "<https://%h/servererror.html>"
}
Figure 4.46 A rule based on certificate status specified in an HTTP header
Header Name Required Format Description
Certificate status SSLClientCertStatus: [status] The status of the client certificate. The value of
[status] can be "NoClientCert", "OK", or "Error".
If status is "NoClientCert", only this header is
inserted into the request. If status is "Error", the
error is followed by a numeric error code.
Certificate version SSLClientCertVersion: [version] The version of the certificate.
Certificate serial
number
SSLClientCertSerialNumber: [serial] The serial number of the certificate.
Signature algorithm of
the certificate
SSLClientCert: [alg] The signature algorithm of the certificate.
Issuer of the certificate SSLClientCert: [issuer] The issuer of the certificate.
Table 4.18 Required formats of client certificate headers
Kommentare zu diesen Handbüchern