[DOCS-6619] x.509 Monitoring Config Missing Steps Created: 19/Nov/15 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Peter Garafano (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 29 weeks ago | ||||
| Epic Link: | docs-auth-x509 | ||||
| Description |
|
When configuration the Monitoring Agent to use x.509 auth (https://docs.cloud.mongodb.com/tutorial/configure-monitoring-agent-for-x509/) it talks about how to config the agent and create the user in the mongod but never how to enable that auth mechanism for a host/replica set/sharded cluster. In the Enable x.509 Authentication for your Cloud Manager Group it only covers how to do it assuming you are under automation. For people not using automation, this does not explain how to turn on x.509 auth. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |