[DOCS-3649] MMS Monitoring/Backup User Auth doesn't cover shard users Created: 25/Jun/14 Updated: 13/Oct/14 Resolved: 13/Oct/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Ryder (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: | 9 years, 19 weeks, 4 days ago | ||||||||||||
| Description |
|
http://mms.mongodb.com/help/reference/authentication/#mms-monitoring This page should explain that the credentials for the MMS agent on a sharded cluster need to be manually propagated down to the shard replica-sets. This step is not required for normal clients because auth normally happens via the config servers. A user can be added to the replica-sets directly via the localhost exception on the respective primaries. The page should also reference the warning (before the step above) that the first user created in each replica-set should be able to create other users. The second user created should be the monitoring agent auth. |
| Comments |
| Comment by Cailin Nelson [ 04/Oct/14 ] |
| Comment by Ronan Bohan [ 19/Sep/14 ] |
|
Hi If I'm not mistaken this problem relates to both MMS Monitoring and MMS BRS. The docs appear to have been updated for MMS BRS only. See in particular the Considerations section on these pages:
I think we still need corresponding documentation for MMS Monitoring:
Ronan |
| Comment by Githook User [ 02/Sep/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 26/Jun/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |