[DOCS-3640] X.509 auth and SSL certificates scope Created: 24/Jun/14 Updated: 24/Feb/16 Due: 08/May/15 Resolved: 29/Apr/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.13 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | security-review | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 years, 42 weeks ago |
| Description |
|
The documentation needs prerequisites (perhaps in the introduction) which spell out that a knowledgeable understanding of X.509 (and PKI / PMI systems in general) is required before attempting to configure X.509 Auth or SSL with MongoDB. We get customers expecting a How-To on setting up such things as a CA (Certificate Authority) which appears to be a reasonable expectation without a background in PKI/PMI systems. MongoDB is not a CA, nor can we provide the appropriate support for customers wanting to set up their own internal CA - this is outside the scope of MongoDB support. It would be useful to say what is required knowledge before attempting to set-up auth or crypto. I suggest a "prerequisites" link at the top of such tutorials that require knowledge of systems outside the scope of MongoDB, for example: |
| Comments |
| Comment by Githook User [ 29/Apr/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 29/Apr/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 29/Apr/15 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 20/Oct/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |