[JAVA-3689] Update Evergreen config to run the new OCSP responder Created: 09/Apr/20  Updated: 28/Oct/23  Resolved: 01/May/20

Status: Closed
Project: Java Driver
Component/s: Security
Affects Version/s: None
Fix Version/s: 4.1.0

Type: Improvement Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: John Stewart (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends

 Description   

Description of Drivers Ticket:

Drivers that already have OCSP tests running in Evergreen will need to update their Evergreen config files to install the flask requirement (via a newly added requirements file) instead of bottlee.g.:

-          ./venv/Scripts/pip3 install asn1crypto oscrypto bottle
+          ./venv/Scripts/pip3 install -r ${DRIVERS_TOOLS}/.evergreen/ocsp/mock-ocsp-responder-requirements.txt

 

[edit: per shane.harvey's suggestion, it would best to store the mock responder's requirements in drivers-evergreen-tools so that future updates to the mock responder's requirements will not require drivers changes]

Drivers that don't yet have OCSP tests running in Evergreen do not need to do anything, as such drivers will use flask from the get-go as  part their initial effort to get OCSP tests running in Evergreen. 

This change is needed due to: mongodb-labs/drivers-evergreen-tools#102 which fixes: mongodb-labs/drivers-evergreen-tools#99 and mongodb-labs/drivers-evergreen-tools#100 and includes changes from: https://jira.mongodb.org/browse/SERVER-46413
and mongodb/mongo#1351

 
See DRIVERS-977 for updated details.



 Comments   
Comment by Githook User [ 01/May/20 ]

Author:

{'name': 'John Stewart', 'email': 'john.stewart@mongodb.com', 'username': 'jstewart-mongo'}

Message: OCSP support

JAVA-3598

Update Evergreen config to run the new OCSP responder

JAVA-3689
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/c932528c23bd0e2e5177d38b9456a35a9b52d921

Generated at Thu Feb 08 09:00:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.