[DOCS-9943] Arbiters Security - Authentication, authorization and access is not clear. Created: 27/Feb/17 Updated: 30/Oct/23 Resolved: 24/Mar/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Idan Sher | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 45 weeks, 5 days ago | ||||
| Description |
|
https://docs.mongodb.com/manual/core/replica-set-arbiter/#security Clarify that the authentication behaviour refers to inter cluster communication only and not to clients/users authenticating to the arbiter. Perhaps add the correct behaviour for clients connecting to an arbiter in a replica set using authentication and authorization. |
| Comments |
| Comment by Sarah Olson [ 24/Mar/23 ] |
|
Closing this out on the grounds that:
Based on this, closing as WON'T DO. Please don't hesitate to give me a shout or to reopen if you disagree. |
| Comment by Kelsey Schubert [ 27/Feb/17 ] |
|
Yes, that's correct. See SERVER-5479 for more details. |
| Comment by Ravind Kumar (Inactive) [ 27/Feb/17 ] |
|
spencer.jackson renctan I vaguely recall that arbiters had some quirks when it comes to clients attempting to authenticate to the instance. Am I right in thinking that the normal auth-connect process may not apply to an arbiter? |