[SERVER-67462] Support renaming encrypted collections if client has correct privileges Created: 22/Jun/22 Updated: 29/Oct/23 Resolved: 07/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.1, 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v6.0
|
||||||||||||||||
| Sprint: | Security 2022-07-11 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In some cases, it may be safe to rename encrypted collections. As a result, we should allow this if the client is properly authenticated. We can potentially do this by tying this functionality to the restore privilege. |
| Comments |
| Comment by Githook User [ 07/Jul/22 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: |