[DOCS-1007] Clarify user access control Created: 17/Jan/13 Updated: 13/Feb/13 Resolved: 13/Feb/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Hows | 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: | 11 years, 1 week, 1 day ago | ||||
| Description |
|
Within the following section of the documentation we cover user access control in a sharded environment. http://docs.mongodb.org/manual/core/sharding/#security-considerations-for-sharded-clusters We need to clarify that when you setup authentication for a sharded database (except for admin) the authentication collection will reside on the primary shard for that db and nowhere else(this is covered somewhat in point 2). We dont clarify that any attempts to authenticate to non-primary members directly will fail. We should probably explain the authentication process a bit here, provide an example of how it works and how to set it up. |
| Comments |
| Comment by auto [ 13/Feb/13 ] |
|
Author: {u'date': u'2013-02-13T00:19:03Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 13/Feb/13 ] |
|
Author: {u'date': u'2013-02-13T00:16:09Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |