correctly handle DNs with components containing commas
Status: Beta
Brought to you by:
bigman921
Our directory has some DNs like cn=Doe\, John, ou=Users, dc=company, dc=com.
There are a few places where MyVD does dn.explodeDN(false) and then creates new RDNs from the pieces. However, that doesn't work for DNs like the one above, because the pieces look like "cn=Doe, John" and new RDN("cn=Doe, John") throws an exception.
This patch makes it encode the piece first, like new RDN(LDAPDN.escapeRDN(currDN[i])). That allows the RDN constructor to process it correctly.
correctly handle DNs with components containing commas
I'll go ahead and add the fix. Can you provide a usecase where you are seeing an error?
Hello. Has this patch been integrated into the binary distribution yet?
Thanks,
Hi, I was wondering how I could either get a version of the software with this patch, or find out how to apply the patch? Getting this same error trying to ldap to several AD servers, and it does not seem to matter which method I use to connect.
Have you tried building from the latest source?
On Jan 21, 2014 5:28 PM, "Jim Scheitel" scheitelj@users.sf.net wrote:
Thank you Marc, that was what I was looking for! Totally cool project. In case anyone else needs to know - install ant and required libs, configured env vars, grab snapshot of newest branch and extract, run ant while in same folder as build.xml. New build is in dist folder. Back up your current configs, blow the existing folder away completely, and copy over the newly built folders to where you want to run from. Add your changes to the configuration back and ~wala... working great.
Last edit: Jim Scheitel 2014-01-22