[SERVER-28972] Relax KeysCollectionManager::getKeyForValidation keyId restriction Created: 25/Apr/17 Updated: 30/Oct/23 Resolved: 13/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.5.7 |
| Fix Version/s: | 3.5.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Misha Tyulenev |
| 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: | Sharding 2017-06-19 | ||||||||
| Participants: | |||||||||
| Description |
|
to allow matching keyId to keys even though they are not the best choice if expiredAt is the only criteria. Example:
In the example above, getKeyForValidation will choose key1 since it has the closest expiredAt for the given time and since the keyId does not match, it will return an error. This scenario should not happen unless key2 was created before key1, which might be possible with |
| Comments |
| Comment by Githook User [ 13/Jun/17 ] |
|
Author: {u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}Message: |