[SERVER-76178] Fix moveRange authorization requirements Created: 17/Apr/23 Updated: 29/Oct/23 Resolved: 18/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 6.0.5, 6.3.0-rc3 |
| Fix Version/s: | 7.0.0-rc0, 7.1.0-rc0, 6.0.6, 6.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| 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 | ||||
| Backport Requested: |
v7.0, v6.3, v6.0
|
||||
| Sprint: | Sharding EMEA 2023-05-01 | ||||
| Participants: | |||||
| Description |
|
In v6.0 the moveRange command has been introduced requiring cluster-wide authorization for the moveChunk action type while the moveChunk command requires per-namespace authorization for the moveChunk action type. Purpose of this ticket is to uniform the authorization policy, changing the moveRange's one to fit the moveChunk's one. |
| Comments |
| Comment by Githook User [ 20/Apr/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 20/Apr/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 20/Apr/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 18/Apr/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |