Download Quest One Quick Connect Virtual Directory Server

5.2. LISTENER CONFIGURATION
In order to make a valid selection here, you will need to have at least one server group defined under the Output
node of the configuration. Remember that server groups contain at least one or more servers that are assumed
to be equivalent. You can read more about server groups in the OUTPUT 6 chapter.
Virtual Tree QC VDS supports the ability to define a virtual tree for any listener. This allows you to design a
completely virtual directory that will be presented to any client connecting to the listener. This facility allows you
to completely abstract the data stored in any backend servergroups so that a client is only aware of the directory
information that you have set out to present. In general this facility would only be used for listeners that have
been configured for the LDAP/S protocol. Although it might be possible to use a Virtual Tree with an alternate
protocol such as HTTP (if building an HTTP to LDAP bridge) if you perform the appropriate processing in a
stage before the Virtual Tree is implemented (see the section Attached Stages 5.2.6). However, the complexity
of such a solution would be an advanced topic and may require support from Quest Software.
In order to use this facility, you will need to create a Virtual Root for your tree and then construct virtual nodes
as you require. Finally, if you wish to include data stored within external repositories, you will need to create
virtual mountpoints, that can be used to import the data into your virtual tree. The ’New Virtual Root’ button can
be used to start constructing your virtual tree. The ’New Virtual Mount Point Root’ button can be used to create
a virtual root that maps directly onto a DN within a particular ServerGroup.
Please see the section How To Use Virtual Trees 5.3 for more information.
5.2.2
Canonicalization
This tab is only meaningful when the LDAP or LDAPS protocol is defined for this listener. Otherwise, this
section will be inactive and unused. It is possible for QC VDS to canonicalize entries coming into QC VDS.
Canonicalization basically means:
1. Trimming spurious whitespaces (i.e. removing whitespaces between DN elements and the commas separating them)
2. Converting attribute names into lowercase
Canonicalization can be very helpful when processing entries. The LDAP model specifies that all LDAP attribute
names are to be treated in a case-insensitive way. Well-behaved LDAP clients will have no problem with canonicalization, although there are a few LDAP clients out there who, contrary to the standard, will not recognize
LDAP attributes in a case-insensitive way. If problems arise with your client applications that point to this type of
behavior, you may want to disable canonicalization or alternatively you can select the check-box which allows
you to ’Canonicalize DN only for processing stages’. If this option is checked, the DN in each PDU will only be
canonicalized as it moves through the processing engine, and will be converted back to its original form before
it is sent either to the ServerGroup or client that it is destined for. While the PDU moves through the processing
engine, the original DN will be stored within the PDU hash for use later.
Figure 5.3: Canonicalization Options
User Reference Manual
48