We have users in AD stored as CN=Doe\, John,OU=Users,DC=domain,DC=com

When using this with mapping and proxy, we end up seeing the users via a ldap browser as CN=Doe\\\ and are unable to access the entry.

I can reproduce with 1.2.5 binary from the nightly build on both windows and linux.  I would just use 1.2.4 but can't use the memberOf ldap filter in 1.2.4.  1.2.4 and bellow do not show this issue. 

I can post the server error output if requested.  Also can post config examples.

Basic setup:  dc=fake,dc=com domain, with mapped LDAP OU's to the ou=User from 3 Active Directory domains.  
Additional Comments From smsource dated Fri May 09 08:39:31 CDT 2008 
The patch in bug PENROSE-262 that is currently applied to the SVN is the cause of the problem.  I don't know java well enough to fix it, but i did remove the code, reverted back to the escaped character code from 1.2.4 and am working fine.


=========================================================
Issue dump from jira
$VAR1 = {
          'priority' => '4',
          'customFieldValues' => [],
          'project' => 'PENROSE',
          'status' => '1',
          'components' => [
                            {}
                          ],
          'reporter' => 'smsource',
          'key' => 'PENROSE-299',
          'assignee' => 'jimyang',
          'summary' => 'Penrose 1.2.5 Proxy of escaped comma's fails',
          'id' => '10994',
          'updated' => '2008-05-09 08:39:31.0',
          'votes' => '0',
          'fixVersions' => [],
          'affectsVersions' => [
                               {
                                 'releaseDate' => '2008-04-14 00:00:00.0',
                                 'sequence' => '27',
                                 'name' => 'Penrose-1.2.5',
                                 'released' => 'true',
                                 'id' => '10124',
                                 'archived' => 'false'
                               }
                             ],
          'description' => 'We have users in AD stored as CN=Doe\\, John,OU=Users,DC=domain,DC=com

When using this with mapping and proxy, we end up seeing the users via a ldap browser as CN=Doe\\\\\\ and are unable to access the entry.

I can reproduce with 1.2.5 binary from the nightly build on both windows and linux.  I would just use 1.2.4 but can't use the memberOf ldap filter in 1.2.4.  1.2.4 and bellow do not show this issue. 

I can post the server error output if requested.  Also can post config examples.

Basic setup:  dc=fake,dc=com domain, with mapped LDAP OU's to the ou=User from 3 Active Directory domains.  ',
          'created' => '2008-05-07 14:24:18.0',
          'environment' => 'Ubuntu JeOS 8.04, JRE 1.6 on VM
WindowsXP Pro, JRE 1.6 on Laptop',
          'type' => '1'
        };


=========================================================