system certificate ocsp-stapling
Use this command to configure OCSP Stapling.
In SSL/TLS connections between the clients (like browsers or apps) and FortiWeb, clients by default check the server certificate presented by FortiWeb, verifying it against a trusted CA store, and contacting the OCSP responder to check whether it is revoked or expired.
While verifying the server certificate’s status through the OCSP responder provides clients with the most up-to-date information, it also introduces an extra network request on the client side. This additional request can increase connection times and lead to noticeable delays in establishing SSL/TLS connections. The diagram below illustrates the SSL connection process between the client and FortiWeb, where the client reaches out to the OCSP responder for the server certificate status.
To improve the efficiency of SSL connections, FortiWeb supports OCSP stapling. In the OCSP stapling process, FortiWeb can be configured to periodically query the OCSP server and cache a time-stamped OCSP response for a specified period. This cached response is then "stapled" to the SSL/TLS handshake, allowing the client to validate the certificate’s status directly through the "stamp" without needing to contact the OCSP responder. The following diagram illustrates the process of OCSP stapling in the SSL connection flow.
This method of verifying the revocation status of certificates shifts the resource cost in providing OCSP responses from the client to the presenter of a certificate. In addition, because fewer overall queries to the OCSP responder will be made when OCSP stapling is configured, the total resource cost in verifying the revocation status of certificates is also reduced.
|
|
OCSP stapling is available in Reverse Proxy, True Transparent Proxy, and WCCP mode. |
Syntax
config system certificate ocsp-stapling
edit <name>
set comment <string>
next
end