-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Security
-
Server Security 2025-11-07, Server Security 2025-11-21, Server Security 2025-12-05
-
None
-
None
-
None
-
None
-
None
-
None
-
None
After an OCSP response acquisition attempt, several events might have occurred:
- A network error
- One or more responder errors
- A response which failed signature validation
- A response which failed to meet policy
- A response which indicates the subject certificate was revoked
- A response which indicates the subject certificate was valid
There are probably a few other edge cases. Currently, the main OCSP stapling loop dispatches requests, then logs message 577163 which includes the Status of acquisition and validation. It doesn't report anything about what was observed in the response, meaning that both valid and revoked responses are reported with Status::OK. This is misleading, and can confuse administrators trying to debug revoked responses.
- is depended on by
-
SERVER-84646 Connecting to OCSP revoked endpoints should fail with server defined errors
-
- Closed
-
- related to
-
SERVER-84646 Connecting to OCSP revoked endpoints should fail with server defined errors
-
- Closed
-