[SERVER-37193] Implement connection pooling for the LDAP servers Created: 18/Sep/18 Updated: 06/Dec/22 Resolved: 24/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrey Brindeyev | Assignee: | Backlog - Security Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Security
|
||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
When configured with an external LDAP authentication & authorization, mongod typically performs three LDAP queries using the separate TCP connections:
The proposed solution is to maintain the connection pool to the external LDAP server and reuse those connections to authenticate the MongoDB clients. The authentication state of a connection needs to be set back to unauthenticated (using an anonymous bind) before the connection will be returned back to the pool. |
| Comments |
| Comment by Jonathan Reams [ 24/Jan/19 ] |
|
In |