[SERVER-61445] OCSP fetcher treats responses without nextUpdate as expired Created: 12/Nov/21 Updated: 29/Oct/23 Resolved: 25/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Erwin Pe | 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 | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Security 2021-11-29 | ||||||||
| Participants: | |||||||||
| Description |
|
If the OCSP fetcher gets an OCSP response without a nextUpdate field, it treats it as an expired response and returns an error here. This error is considered transient, and the fetcher will try again after some duration determined by the retry backoff counter. |
| Comments |
| Comment by Githook User [ 25/Nov/21 ] |
|
Author: {'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}Message: |