Previous Topic

Next Topic

Book Contents

Multi Verifier Example 3

In the following Multi verifier, there are again two LDAP directories to search. Neither one will be enumerated because the <Multi> parent is missing the critical <InterEnumTime> element. When this Multi verifier is loaded on a server with a default route matching 172.30.1.*, then for each verification request, it will query server 10.111.1.12 then 10.10.1.243 if there was no match found.

When the same Multi verifier is loaded on a server that does not have a default route in 172.30.1.*, then it will try to connect to 168.11.164.244. When no match is found for an email address, the search will be sent to 168.11.164.243.

<Vrfy version="101.4635">

<Multi>

<LDAP defaults="ActiveDirectory">

<Host defaultRouteMatch="172\.30\.1\.[0-9]+">10.111.1.12</Host>

<Host defaultRouteNoMatch="172\.30\.1\.[0-9]+">168.11.164.244</Host>

<credentials>

<Username>redcondor@qqab.local</Username>

<EncPass>53616c74b374218a60056</EncPass>

</credentials>

<BaseDN>DC=sites,DC=QQAB,DC=local</BaseDN>

</LDAP>

<LDAP defaults="ActiveDirectory">

<Host defaultRouteMatch="172\.30\.1\.[0-9]+">10.10.1.243</Host>

<Host defaultRouteNoMatch="172\.30\.1\.[0-9]+">168.11.164.243</Host>

<credentials>

<Username>redcondor@qqab.local</Username>

<EncPass>53616c7465645374218a60056</EncPass>

</credentials>

<BaseDN>DC=QQAB,DC=local</BaseDN>

</LDAP>

</Multi>

</Vrfy>