New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JNDI DN incorrect backslash escaping #119

Closed
dfish3r opened this Issue Nov 7, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@dfish3r
Copy link
Member

dfish3r commented Nov 7, 2016

DNs are parsed through a CompositeName for character escaping.
Since backslash is a meta character in JNDI, CompositeName will consume backslashes that are meant for escaping.

dfish3r added a commit that referenced this issue Nov 8, 2016

@dfish3r

This comment has been minimized.

Copy link
Member

dfish3r commented Nov 8, 2016

@dfish3r dfish3r closed this Nov 8, 2016

dfish3r added a commit that referenced this issue Dec 18, 2018

Use LdapName instead of String for base DN.
LdapContext delegates to CompositeName, not LdapName for search methods.
CompositeName comsumes backslashes that are meant for escaping.
See #144 and #119.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment