[SERVER-49537] OCSP Validation with empty nextUpdate field Created: 16/Jul/20 Updated: 29/Oct/23 Resolved: 15/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Shreyas Kalyan | Assignee: | Erwin Pe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 2021-11-15, Security 2021-11-29 | ||||||||
| Participants: | |||||||||
| Description |
|
When initializing the mock OCSP responder, there is a parameter for the next_update_seconds. If that value is 0 or negative, the next update field on the OCSP response should not be set. |
| Comments |
| Comment by Githook User [ 15/Nov/21 ] |
|
Author: {'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}Message: |
| Comment by Shreyas Kalyan [ 03/Nov/20 ] |
|
I have updated the ticket description to clarify what I want from this ticket. |
| Comment by Spencer Jackson [ 03/Nov/20 ] |
|
shreyas.kalyan can you clarify the description on this ticket? Are you asking for a new flag for the responder? |