Description |
This article describes how to troubleshoot OCSP issues in FortiWeb. |
Scope |
FortiWeb 7.0.0 and later. |
Solution |
If OCSP stapling is enabled on FortiWeb but not on the web server (e.g., Apache, Nginx), the server might not be providing the stapled OCSP response. Ensure that the web server is configured to support OCSP stapling.
Commands such as 'openssl s_client -connect testsites.com:443 -status' can be used to verify if the server is returning a stapled OCSP response.
This command checks whether the server is returning a stapled OCSP response. Look for the OCSP Response Status: successful in the output to confirm that the response is correctly returned. If not, further investigate the server configuration.
FortiWeb must be able to communicate with the OCSP responder (the CA's server issuing the certificates). Check for firewall rules or network issues that may prevent this communication, as it could cause OCSP stapling to fail.
Investigate any network problems, DNS resolution issues, or firewalls that may block communication between FortiWeb and the OCSP responder.
Confirm that the CA issuing the certificate supports OCSP and provides timely responses. OCSP stapling may fail if the CA’s responder is down or experiencing delays. Ensure the certificate is correctly configured with OCSP URLs in its AIA (Authority Information Access) field.
Analyze FortiWeb event logs to identify any issues related to OCSP.
Related document: |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.