[DOCS-6213] mongos --sslAllowInvalidHostnames says mongoses connect to mongoses Created: 15/Sep/15 Updated: 26/Jul/18 Resolved: 17/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 4 weeks, 1 day ago |
| Description |
|
https://docs.mongodb.org/manual/reference/program/mongos/#cmdoption--sslAllowInvalidHostnames
But mongoses don't connect to other mongoses. Looks like this was copied from the equivalent mongod argument. The quickest fix would just be "... when connecting to mongod instances for inter-process authentication. This allows mongos to connect to mongod instances ...". A more comprehensive fix would be to change both the mongos and mongod docs to say something like "... when connecting to other MongoDB instances for inter-process authentication in a replica set or sharded cluster. This allows mongod/mongos to connect to other MongoDB instances ...". |
| Comments |
| Comment by Kay Kim (Inactive) [ 17/Jan/18 ] |
|
Will publish tomorrow |
| Comment by Githook User [ 17/Jan/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 17/Jan/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 17/Jan/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 17/Jan/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |