[COMPASS-7197] Investigate changes in SERVER-72839: Server skips peer certificate validation if neither CAFile nor clusterCAFile is provided Created: 07/Sep/23 Updated: 28/Jan/24 Resolved: 11/Sep/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Investigation | Priority: | Minor - P4 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Documentation Changes: | Not Needed | ||||||||
| Description |
|
Original Downstream Change Summary Connections that previously worked due to Cert checking failing to occur (where the check should have failed but didn't) may no longer work. Description of Linked TicketThe documentation says that: If --tlsCAFile or tls.CAFile is not specified and you are not using x.509 authentication, the system-wide CA certificate store will be used when connecting to an TLS-enabled server. However, when a server is configured with neither CAFile nor clusterCAFile, it will skip peer certificate validation on both ingress and egress TLS connections. The expectation is that on egress connection, the node (client) should at least verify the peer (server's) certificate using the system CA cert store. Note, this only applies to server processes (mongod and mongos), the shell is not affected. |
| Comments |
| Comment by PM Bot [ 28/Jan/24 ] |
|
Fix Version updated for upstream |
| Comment by PM Bot [ 28/Jan/24 ] |
|
Fix Version updated for upstream |
| Comment by PM Bot [ 27/Jan/24 ] |
|
Fix Version updated for upstream |
| Comment by PM Bot [ 27/Jan/24 ] |
|
Fix Version updated for upstream |
| Comment by PM Bot [ 28/Sep/23 ] |
|
Fix Version updated for upstream |