[SERVER-51426] Verify that a client cannot gossip clusterTime from a donor replica set to a recipient replica set Created: 07/Oct/20 Updated: 29/Oct/23 Resolved: 19/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_milestone-F | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-10-19, Sharding 2020-11-02 |
| Participants: |
| Description |
|
The client should not be able to gossip a clusterTime from donor to recipient, since the donor and recipient replica sets should have different secret keys. This ticket is to confirm that if the client first does an operation against the donor and gets back a time signed by the donor, then does an operation against the recipient, then the recipient rejects the client's operation because the client's time was signed by a different key. |
| Comments |
| Comment by Githook User [ 19/Oct/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |