Bug 830349 – cannot use & in a sasl map search filter

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 830349 - cannot use & in a sasl map search filter

Summary:	cannot use & in a sasl map search filter

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	389-ds-base (Show other bugs)
Sub Component:
Version:	6.4
Hardware:	Unspecified Unspecified

Priority	medium Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Rich Megginson
QA Contact:	Sankar Ramalingam
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-06-08 17:43 EDT by Nathan Kinder
Modified:	2013-02-21 03:17 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	389-ds-base-1.2.11.12-1.el6
Doc Type:	Bug Fix
Doc Text:	Cause: Using a compound search filter (with an ampersand "&" character) for the SASL mapping, the "&" was not escaped properly. Consequence: SASL mapping fails to map the SASL identity to a DN, and SASL authentication fails. Fix: check for '&', and don't escape it. Result: mapping succeeds
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-02-21 03:17:52 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2013:0503	normal	SHIPPED_LIVE	Moderate: 389-ds-base security, bug fix, and enhancement update	2013-02-21 03:18:44 EST

Groups: None (edit)

Description Nathan Kinder 2012-06-08 17:43:50 EDT

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/291

I have a need to use a search filter in SASL mappings where it looks like something
{{{
(&(uid=\1)(|(objectclass=x)(objectclass=y)))
}}}
the & is being substituted like \1 as seen with tracing turned on.  I have tried escaping it as \& and \\&.  I can't find any documentation on how the substitution is handled with the filter.  Is it not possible to utilize a normal ldap search filter like this in SASL mappings?

Comment 1 RHEL Product and Program Management 2012-07-10 02:17:57 EDT

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 2 RHEL Product and Program Management 2012-07-10 19:00:59 EDT

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 3 Ján Rusnačko 2012-08-13 09:25:32 EDT

bug830349 in sasl/sasl-qa.sh

Comment 5 Ján Rusnačko 2012-11-01 09:25:52 EDT

IP=192.168.122.86
PORT=22222

ldapmodify -h $IP -p $PORT -D "cn=directory manager" -w Secret123 <<-EOF 
dn: cn=mymap1,cn=mapping,cn=sasl,cn=config
changetype: add
objectclass: top
objectclass: nsSaslMapping
cn: mymap1
nsSaslMapRegexString: .*
nsSaslMapBaseDNTemplate: ou=TestPeople, o=sasl.com
nsSaslMapFilterTemplate: (|(&(uid=\1)(objectclass=person))(&(uid=\1)(objectclass=inetOrgPerson)))
EOF

/usr/lib64/dirsrv/slapd-dstet/restart-slapd

[jrusnack@dstet 6.0]$ ldapsearch -LLL -h $IP -p $PORT -D "cn=directory manager" -w Secret123 -b "cn=mymap1,cn=mapping,cn=sasl,cn=config" cn
dn: cn=mymap1,cn=mapping,cn=sasl,cn=config
cn: mymap1

[jrusnack@dstet 6.0]$ echo $?
0

[jrusnack@dstet 6.0]$ rpm -qa  | grep 389-ds-base
389-ds-base-1.2.11.15-2.el6.x86_64

Comment 7 errata-xmlrpc 2013-02-21 03:17:52 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0503.html

Note You need to log in before you can comment on or make changes to this bug.