[DOCS-4683] Minimum example for how to use x.509 Certificates to Authenticate Clients should not use --clusterAuthMode Created: 16/Jan/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Cailin Nelson | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 1 |
| Description |
|
Using x.509 for cluster authentication is tricky, and is not a prerequisite to using it for client authentication. It seems like our examples for using x.509 for client authentication should not include the --clusterAuthMode parameter. This is placing an unnecessary and orthogonal burden on the user trying to follow the example. |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Lungang Fang [ 17/Aug/18 ] |
|
I was reading Use x.509 Certificates to Authenticate Clients and found the section Configure Replica Set/Sharded Cluster was misleading. The clusterAuthMode: x509 is for member authentication not for client authentication. |