[SERVER-28369] Give mongoldap a 'debug' mode Created: 17/Mar/17 Updated: 02/Apr/18 Resolved: 17/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Security |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.15, 3.5.5 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Spencer Jackson |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v3.4
|
||||
| Sprint: | Platforms 2017-03-27 | ||||
| Participants: | |||||
| Description |
|
The mongoldap tool is intended to produce useful, clear, reports for administrators setting up or debugging LDAP AuthZN deployments. However, if an issue arises in the actual implementation of the LDAP integration, noisy, unclear, diagnostic information would be useful. It should be possible to invoke mongoldap with '--debug' to print all the low priority informational messages printed by the LDAP subsystem. |
| Comments |
| Comment by Githook User [ 29/Mar/18 ] |
|
Author: {'email': 'spencer.jackson@mongodb.com', 'name': 'Spencer Jackson', 'username': 'spencerjackson'}Message: (cherry picked from commit 61e10ac03b9e844834419e256a87dcdb1d559bfa) |
| Comment by Githook User [ 17/Mar/17 ] |
|
Author: {u'username': u'spencerjackson', u'name': u'Spencer Jackson', u'email': u'spencer.jackson@mongodb.com'}Message: |