[DOCS-8249] rs.initiate() needed before db.createUser() using localhost exception if node is fresh replset node Created: 12/Jul/16 Updated: 30/Oct/23 Resolved: 01/Feb/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Akira Kurogane | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 2 weeks ago |
| Story Points: | 0.5 |
| Description |
|
The "Add Users After Enabling Access Control" section of /manual/tutorial/enable-authentication/ describes how to create the first user after creating a new node that has auth enabled. I think the list of steps should include a new one between the current steps 2 and 3, pointing out if the node has the replSet arg (i.e. it is the first node of new replica set being created) that rs.initiate() will need to be run as the first step, before db.createUser(). If it isn't then no writes will be permitted (the node is not yet a primary), so the db.createUser() command will be refused for that reason. Without that caveat users may think the error they see when they run db.createUser() is something they did wrong in regards to options they set or how well they followed our instructions. |
| Comments |
| Comment by Kay Kim (Inactive) [ 01/Feb/18 ] |
|
will publish tomorrow |
| Comment by Githook User [ 01/Feb/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by Akira Kurogane [ 31/Jan/18 ] |
|
Hi Kay. Yes, I am. Thanks for your effort and care on this request! |