[DOCS-193] Security and Authentication page wording implies you can use auth without keyFiles Created: 27/Apr/12 Updated: 13/Jun/12 Resolved: 13/Jun/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (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: | 11 years, 36 weeks ago | ||||||||
| Description |
|
The wording on this page http://www.mongodb.org/display/DOCS/Security+and+Authentication implies that you can use --auth without --keyFile. In particular, here http://www.mongodb.org/display/DOCS/Security+and+Authentication#SecurityandAuthentication-ReplicaSetandShardingAuthentication , the beginning says "Replica sets and sharding can use authentication...." note "can." At the end of the section, where it explains that keyFile implies auth, but not vice versa, it again sounds like I can run with auth (plain), or with keyFile (which implies auth). Got a customer who's trying to do this and its failing. In an email thread on the subject, Scott said "Yes, you cannot use authentication without keyfile on a replicaset or sharded cluster. The keyfiles is the auth part when it is not initiated from a user – like replication or chunk migration." This should be added to the page, and the wording changed so the choice is not implied. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 13/Jun/12 ] |
|
Dwight's refactor of this page resolved this issue. |
| Comment by Sam Kleinman (Inactive) [ 30/Apr/12 ] |
|
Chris, It looks like your recent edits to the Security and Authentication section resolves this issue, am I correct or is there additional work to be done? |