[DOCS-9300] Comment on: "mms/tutorial/edit-replica-set.txt" (Security clarification) Created: 10/Nov/16 Updated: 30/Jan/17 Resolved: 26/Jan/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Vick Mena (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.opsmanager.mongodb.com/current/tutorial/edit-replica-set/ |
||
| Participants: | |
| Days since reply: | 7 years, 2 weeks, 2 days ago |
| Epic Link: | C/OM Security |
| Story Points: | 0.25 |
| Description |
|
When extending a replica set which is using SSL at the process level and managed through automation it is not clearly stated that the SSL keys/certs/etc are not automatically sent to the new node. It makes sense however it would be good to clearly state this fact to avoid a failure after "Review and Deploy." |
| Comments |
| Comment by Githook User [ 30/Jan/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |
| Comment by Githook User [ 30/Jan/17 ] |
|
Author: {u'username': u'atsansone', u'name': u'Tony Sansone', u'email': u'tony.sansone@mongodb.com'}Message: ( |