Modifying Default Search Filters - Red Hat DIRECTORY SERVER 7.1 - GATEWAY CUSTOMIZATION Manual

Modifying Default Search Filters

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