[SERVER-4601] The mongo console requires authentication even if mongod is not started with --auth Created: 03/Jan/12 Updated: 17/Feb/17 Resolved: 17/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | HTTP Console |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Barrie Segal | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Won't Fix | 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 | ||||||||
| Participants: | |||||||||
| Description |
|
To reproduce: Start up mongod with no flags In a local mongo JS shell remove any user credentials from all dbs, including admin > use admin With another computer on the network (or a VM) open a browser and go to the mongo console of the machine that is running mongod You should be able to access the console. Now, clear the browser history and close the browser in the second computer or VM In the JS console of the machine running mongod, create a new user in the admin database. > use admin Go back to the second computer or VM, and try to access the console. Notice that an "authentication" window pops up. The HTTP interface documentation states that, "If security is configured for a mongod instance, authentication is required for a client to access the http interface from another machine." http://www.mongodb.org/display/DOCS/Http+Interface#HttpInterface-HTTPConsoleSecurity If this behavior is by design, the documentation should be changed to reflect that authentication will be required even if mongod is not started with the --auth flag. |
| Comments |
| Comment by Mira Carey [ 17/Feb/17 ] |
|
The HTTP interface has been deprecated for several releases (as of 3.2) and we're not planning any further development |