[DOCS-2460] add warning against changing system collections when auth is disabled Created: 30/Dec/13 Updated: 16/Mar/15 Resolved: 10/Apr/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Michael O'Brien | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 44 weeks, 5 days ago | ||||
| Description |
|
in 2.6 the auth collections (system.users, system.roles, etc) are protected from being modified directly, as long as auth is enabled. However, if you restart the node with auth disabled, it's possible to insert/remove/modify the collections which can screw things up. We might want to have a warning somewhere in the auth docs telling people not to do this. |
| Comments |
| Comment by Githook User [ 11/Apr/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 11/Apr/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |