tracker issue : CF-4203349

select a category, or use search below
(searches all categories and all time range)
Title:

CF 2016 injecting backslash into response from LDAP server

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/AsDesigned

Reporter/Name(from Bugbase): ryandotdee . / ()

Created: 09/21/2018

Components: Net Protocols, LDAP

Versions: 2016,11.0,2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: 6 /

Priority/Frequency: Normal / All users will encounter

Locale/System: ALL / Win 2016

Vote Count: 0

Problem Description:

When using the CFLDAP tag, we have noticed that on certain responses CFLDAP is injecting a backslash into the response.  We have run a test harness on CF 9 and the problem is not present

Steps to Reproduce:

LDAP query using CFLDAP
filter="(&(objectclass=dnsrrset)(cn=srv=_DOMAINNAME._tcp))"

Actual Result:

cn=srv\=_sipfederationtls._tcp, cn=leeabbey.org.uk, ou=dns, o=eclipse.co.uk

Expected Result:

cn=srv=_sipfederationtls._tcp, cn=leeabbey.org.uk, ou=dns, o=eclipse.co.uk 

Any Workarounds:

None that we have found to stop it happening, we have had to put specific code in place to strip this slash out.  We suspect it is something to do with the format of the query being  

cn=srv=

However, this is a valid LDAP query.

Attachments:

Comments:

I have tried it with couple of LDAP servers both are storing the LDAP DN with the escaped equals character in DN. LDAP standard says to escape few special characters with backslash. Looks like the LDAP servers following the same. The below screenshot is from Apache Directory server.   !image-2019-05-13-16-57-07-832.png!
Comment by S V.
30756 | May 13, 2019 11:27:27 AM GMT