[SERVER-11075] Allow access to arbiters when auth is enabled Created: 08/Oct/13 Updated: 08/Oct/13 Resolved: 08/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Cailin Nelson | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, if an arbiter is part of a replica set with auth enabled, it can only be accessed by other members of the set. Users cannot authenticate against the arbiter to run any administrative commands (except for db.isMaster). A user should be able to authenticate to an arbiter and run administrative commands such as db.serverStatus. This could be implemented by allowing the arbiter to verify the user's auth credentials against the primary of the set. |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 08/Oct/13 ] |
|
dup of SERVER-5479 |