vmware-tanzu-labs/cf-mgmt

setting log level to debug causes LDAP sync to fail; bug fixed in go-ldap upstream

Proplex opened this issue · 2 comments

Describe the bug
Currently, if a user sets log_level to DEBUG, LDAP syncing will fail out with the error:

LDAP Result Code 203 "Debugging Error": ldap: cannot process packet to add descriptions

This is a known issue with the LDAP library that cf-mgmt uses, and was fixed in later versions of the library. It appears we're using v3.0.3, and the bug appears to have been fixed in v3.1.7.

Is there any chance y'all have the bandwidth to update to the new library? I understand this is a really niche request, but would be really appreciated. Thank you!

To Reproduce
Steps to reproduce the behavior:

  1. Set CF-mgmt logging output to DEBUG
  2. Configure CF-mgmt to use LDAP syncing
  3. Execute either update-org-users or update-space-users
  4. See error

Expected behavior
A successful execution of CF mgmt, including debug output.

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

This is now working as of the latest cf-mgmt release, thank you!