ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1025
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Security
    • Fully Compatible
    • ALL
    • Server Security 2026-11-06
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      BF-47001: ocsp_basic_ca_responder.js failed on enterprise-windows (v8.3-staging @ 5d60fa4c) with did not throw exception at line 52, during the second test() call (intermediate-CA chain). The shell connected to mongod even though the mock OCSP responder was set to report the server cert as revoked.

      Likely cause

      The shell's revocation check seems to have hit the 4s default tlsOCSPVerifyTimeoutSecs (passed to Windows as dwUrlRetrievalTimeout). The test sets no CRL, so a timed-out check counts as "revocation unknown", which is ignored, and the connection succeeds (soft fail).

      Timeline from the test log:

      • 03:43:02.687: TLS handshake completes; the shell starts checking the server cert
      • 03:43:04.696: the mock receives the OCSP GET (~2s later) and replies revoked
      • 03:43:06.689: the shell accepts the cert, exactly 4.000s after the handshake

      Every OCSP request in this run arrives ~2s after its handshake, and Windows sometimes ignores the first response and retries 2s later. In the failing case, the retry would have gone out after the 4s deadline.

      Proposed fix

      Raise the OCSP verify timeout in this test, for both mongod and the shell (e.g. tlsOCSPVerifyTimeoutSecs: 10), so slow lookups don't silently soft-fail. 

            Assignee:
            Adrian Gonzalez Montemayor
            Reporter:
            Adrian Gonzalez Montemayor
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: