[SERVER-11018] Auth behavior of mergeChunks command is inconsistent with splitChunk Created: 03/Oct/13 Updated: 11/Jul/16 Resolved: 03/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.3 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | David Storch | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||
| Operating System: | ALL | |||||||||||||
| Steps To Reproduce: | 1) run mongod with --auth
4)
5) use test 6)
7)
This exposes the problem, because the auth error checking happens before checking that sharding is enabled. |
|||||||||||||
| Participants: | ||||||||||||||
| Description |
|
Both the mergeChunks command and the splitChunk command require the clusterAdmin role. When logged in as a user with the clusterAdmin role, splitChunk can only be run on the admin database. MergeChunks, however, can be run on any database. In order to be consistent, mergeChunks should return a "not authorized" error when run on any database other than admin. |
| Comments |
| Comment by auto [ 03/Oct/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |
| Comment by Greg Studer [ 03/Oct/13 ] |
|
issue is mergeChunks command needs to implement "adminOnly" virtual method. |