[SERVER-32933] Allow mongod to start when unable to reach LDAP server Created: 26/Jan/18 Updated: 29/Oct/23 Resolved: 02/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | 3.4.10, 3.6.2 |
| Fix Version/s: | 3.4.14, 3.6.3, 3.7.2 |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Cory Mintz | Assignee: | Spencer Jackson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | mms-s | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v3.6, v3.4
|
||||||||||||||||
| Sprint: | Platforms 2018-01-29, Platforms 2018-02-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
When using "SCRAM-SHA-1, PLAIN" as your authentication mechanism it would be desirable for mongod to start and continue to run, regardless of the state of the LDAP server since SCRAM users will still be able to authenticate. Currently there is a check on startup of mongod that will prevent the server from starting when the LDAP server can not be validated.
|
| Comments |
| Comment by Githook User [ 06/Mar/18 ] |
|
Author: {'email': 'spencer.jackson@mongodb.com', 'name': 'Spencer Jackson', 'username': 'spencerjackson'}Message: (cherry picked from commit 7245a9bace0a753e8564fa2101de12073baf7349) |
| Comment by Githook User [ 08/Feb/18 ] |
|
Author: {'email': 'spencer.jackson@mongodb.com', 'name': 'Spencer Jackson', 'username': 'spencerjackson'}Message: (cherry picked from commit 7245a9bace0a753e8564fa2101de12073baf7349) |
| Comment by Githook User [ 02/Feb/18 ] |
|
Author: {'email': 'spencer.jackson@mongodb.com', 'name': 'Spencer Jackson', 'username': 'spencerjackson'}Message: |