Installation guide

Modifying Default Search Filters
76 Red Hat Directory Server Gateway Customization Guide • April 2005
not-used-by-dsgw
not-used-by-dsgw
subtree
"name" "cn" 111111 "" ""
"location" "l" 111111 "" ""
"occupant" "roleOccupant" 111111 "" ""
"description" "description" 111011 "" ""
"phone number" "telephoneNumber" 111011 "" ""
END
"is" "(%a=%v))"
"is not" "(!(%a=%v)))"
"sounds like" "(%a~=%v))"
"starts with" "(%a=%v*))"
"ends with" "(%a=*%v))"
"contains" "(%a=*%v*))"
END
The syntax in the above example specifies a list of filters for searching attributes in the
OrgRole object class.
This example creates a new
dsgwfilter.conf entry for OrgRole:
dsgwfilter.conf:
dsgw-orgrole"
"=" " " "(%v))" "LDAP filter is"
"^[+]*[0-9][ 0-9-]*$" "
" "(telephoneNumber=*%v))" "phone number ends with"
"^\*$" " " "(cn=*))" "name is"
".*" ". _" "(cn=%v1-))" "name is"
"(cn=*%v1-*))" "name contains"
"(cn~=%v1-))" "name sounds like"
Modifying search results forms is described in “Modifying Search Result Templates,” on
page 80.
Modifying Default Search Filters
The gateway uses dsgwflter.conf to map patterns in search strings to a relevant search
filter and search result description (a search pattern is a grep-style regular expression).
dsgwwfilter.conf can be optimized to respond to common user data patterns.
Modify existing search filters in
dsgwfilter.conf to support new user data patterns
instead of creating new filters.
The sections that follow explain: