Skip to content

Conversation

@CravateRouge
Copy link
Contributor

Option to send already encoded values calling MSLDAPClient.modify. Disabled by default to not disturb tools already using this function.
I also added LDAP_WELL_KNOWN_ATTRS in the available lookup tables to increase encoding possibilities

@CravateRouge CravateRouge deleted the patch-3 branch March 14, 2025 13:40
@CravateRouge CravateRouge restored the patch-3 branch March 16, 2025 07:23
@CravateRouge CravateRouge reopened this Mar 16, 2025
@skelsec
Copy link
Owner

skelsec commented Oct 29, 2025

is this one still needed?
What do you think of a solution that instead of introducing a new input variable we could allow the users to send a custom object like LDAPCustomValue that has an encode method which the user can implement the encoding logic in?

@CravateRouge
Copy link
Contributor Author

That's a very good idea, it's even more flexible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants