Menu

#2 correctly handle DNs with components containing commas

open-accepted
nobody
None
5
2014-01-21
2010-11-11
No

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.

Discussion

  • Nathan Rogers

    Nathan Rogers - 2010-11-11

    correctly handle DNs with components containing commas

     
  • Marc Boorshtein

    Marc Boorshtein - 2010-12-30

    I'll go ahead and add the fix. Can you provide a usecase where you are seeing an error?

     
  • Marc Boorshtein

    Marc Boorshtein - 2010-12-30
    • status: open --> open-accepted
     
  • David Torre

    David Torre - 2011-02-04

    Hello. Has this patch been integrated into the binary distribution yet?

    Thanks,

     
  • Jim Scheitel

    Jim Scheitel - 2014-01-21

    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.

     
    • Marc Boorshtein

      Marc Boorshtein - 2014-01-22

      Have you tried building from the latest source?
      On Jan 21, 2014 5:28 PM, "Jim Scheitel" scheitelj@users.sf.net wrote:

      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.


      Status: open-accepted
      Created: Thu Nov 11, 2010 04:28 PM UTC by Nathan Rogers
      Last Updated: Mon Jan 06, 2014 01:38 PM UTC
      Owner: nobody

      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.


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/myvd/patches/2/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       
      • Jim Scheitel

        Jim Scheitel - 2014-01-22

        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

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.