[DOCS-1305] Tools now take --authenticationDatabase option and may need it Created: 27/Mar/13 Updated: 08/May/13 Resolved: 08/May/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 41 weeks ago | ||||
| Description |
|
The tools used to automatically try to authenticate to the admin database when auth failed on an ordinary database. They no longer do so. The tools now take an --authenticationDatabase option to say what db to use a username/password pair with. This tightening was intended, but could be considered a regression for some use cases. See: https://jira.mongodb.org/browse/FREE-25302 The release notes ought to mention that some uses of the tools now need to explicitly specify "--authenticationDatabase admin" to get server-wide or cluster-wide access. |
| Comments |
| Comment by auto [ 08/May/13 ] |
|
Author: {u'date': u'2013-05-08T18:57:57Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |