[SERVER-60225] mock_ocsp_responder must log activity Created: 24/Sep/21  Updated: 29/Oct/23  Resolved: 01/Oct/21

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Sergey Galtsev (Inactive) Assignee: Sergey Galtsev (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Security 2021-10-04
Participants:
Linked BF Score: 47

 Description   

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



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 01/Oct/21 ]

Author:

{'name': 'Sergey Galtsev', 'email': 'sergey.galtsev@mongodb.com', 'username': 'brushless-glitch'}

Message: SERVER-60225 increase verbosity of mock OCSP responder
Branch: master
https://github.com/mongodb/mongo/commit/90083f91b3beac0a7d3966b5c3a1e9dbb3355504

Generated at Thu Feb 08 05:49:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.