[SERVER-29923] SASL authentication session factory should use dynamically LDAP server list Created: 29/Jun/17 Updated: 30/Oct/23 Resolved: 02/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security, Usability |
| Affects Version/s: | 3.4.5 |
| Fix Version/s: | 3.7.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Spencer Jackson |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Platforms 2018-02-12 | ||||
| Participants: | |||||
| Description |
|
The SASL authentication session factory uses the presence of an LDAP server in the startup flags to figure out if it should route PLAIN authentication attempts on $external to the native LDAP authentication code. However, if no LDAP server was set on startup, but one was specified dynamically via a setParameter, the factory will not realize that it can produce a native LDAP SASL session, and will incorrectly produce a CyrusSasl authentication session, which will try to use saslauthd which may not be configured. |
| Comments |
| Comment by Githook User [ 02/Feb/18 ] |
|
Author: {'email': 'spencer.jackson@mongodb.com', 'name': 'Spencer Jackson', 'username': 'spencerjackson'}Message: |
| Comment by Githook User [ 11/Aug/17 ] |
|
Author: {'name': 'Tyler Kaye', 'email': 'tyler.kaye@mongodb.com'}Message: |
| Comment by Githook User [ 11/Aug/17 ] |
|
Author: {'name': 'Tyler Kaye', 'email': 'tkaye@princeton.edu'}Message: Revert " This reverts commit 880e3c102363611ef09b451737276c0ad9400d11. |
| Comment by Tyler Kaye [ 10/Aug/17 ] |
|
URI Parsing ticket was mistakenly pushed with this Server Ticket Number. If you are looking for that ticket please see |