[DOCS-6025] Comment on: "manual/tutorial/configure-x509-member-authentication.txt" Created: 13/Aug/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: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | bite-sized, docs-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ubuntu 14.04. mongo 3.0.5 / wired tiger. Using server, cluster and client certificates signed by a CA. Location: http://docs.mongodb.org/manual/tutorial/configure-x509-member-authentication/ |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 0.25 |
| Description |
|
I couldn't add a member on a new mongo server with x509 cluster authentication enabled until I made the O, OU (and DC) attributes of the certificates match those of the server KEYPemFile. When they differ, the server to be added returns a 'could not find user' error. The description says that the O, OU and DC attributes need to match within the cluster certificates, but doesn't mention that they should match the server certificates also. |
| 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! |