preserve tuples for ldap modification operations #48258
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Preserves the tuples which are passed into the decoding method for ldap modify operations
What issues does this PR fix or reference?
Fixes #46887 (comment)
Specifically:
Which I traced to this in modules/ldap3.py before & after the utils.data.decode:
Notice that the inner tuple gets converted to a list which the underlying ldap library isn't fond of
Turning on preserve_tuples fixes the issue
Previous Behavior
ldap modify operations fail
New Behavior
ldap modify operations succeed
Tests written?
No
Commits signed with GPG?
No