[DOCS-11111] Certificate designation is incorrect for --sslPEMKeyFile option Created: 11/Dec/17 Updated: 29/Oct/23 Resolved: 29/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | BI Connector |
| Affects Version/s: | 2.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Luke Prochazka | Assignee: | Steve Renaker (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | security | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
https://docs.mongodb.com/bi-connector/current/faq/index.html#connecting-a-client-to-mongosqld |
||
| Participants: | |
| Days since reply: | 6 years, 2 weeks, 2 days ago |
| Story Points: | 0.1 |
| Description |
|
Located on all v2.x docs, for the Connecting a client to mongosqld. The text describing the use of the --sslPEMKeyFile option was copied from the previous section, however the role of the certificate is reversed and the description is now misleading. I would recommend replacing "client certificate" with "server certificate" and "mysql_client.pem" with either "mysqld_server.pem" or "mongosqld_server.pem". |
| Comments |
| Comment by Steve Renaker (Inactive) [ 29/Jan/18 ] |
| Comment by Caleb Thompson [ 11/Dec/17 ] |
|
Duplicate of https://jira.mongodb.org/browse/DOCS-10559 |