Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-60225

mock_ocsp_responder must log activity

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: Security
    • Labels:
      None
    • Fully Compatible
    • Security 2021-10-04
    • 47

      Re: BF-22685

      Presently the mock_ocsp_responder shell component output looks like this:

      [js_test:ocsp_must_staple] sh73536| Initializing OCSP Responder
      [js_test:ocsp_must_staple] sh73536|  * Serving Flask app "mock_ocsp_responder" (lazy loading)
      [js_test:ocsp_must_staple] sh73536|  * Environment: production
      [js_test:ocsp_must_staple] sh73536|    WARNING: This is a development server. Do not use it in a production deployment.
      [js_test:ocsp_must_staple] sh73536|    Use a production WSGI server instead.
      [js_test:ocsp_must_staple] sh73536|  * Debug mode: off
      [js_test:ocsp_must_staple] sh73536|  * Running on http://127.0.0.1:8100/ (Press CTRL+C to quit)
      

      We need to update mock_ocsp_responder to output details of requests and responses, so that it is easier to understand what exactly is going on during failed tests

            Assignee:
            sergey.galtsev@mongodb.com Sergey Galtsev (Inactive)
            Reporter:
            sergey.galtsev@mongodb.com Sergey Galtsev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: