Kofax Front-Office Server 3.0 - Manual (Page 41)

Kofax Front-Office Server Administrator’s Guide
Kofax, Inc. 41
Figure 11. Database table: customemailfaxlookup
Active Directory or LDAP Lookup
Based on the search entry, the directory service search returns user and group information, which
includes email addresses and fax numbers. Of course, for configurations not using directory
services nothing will be returned for this source.
If you use Active Directory, there are no configuration steps: connection and lookup capability is
automatic. If you use LDAP, you must specify the name of the attributes that contain email
address and fax number in \conf\avalin_security.properties.
These are the email and fax attributes in the avalin_security.properties file:
###############################################################
# Attributes for fax and email
###############################################################
userFaxAttribute=
userEmailAttribute=
groupFaxAttribute=
groupEmailAttribute=
Contacts List Lookup
If Contacts search is enabled, users can search their Microsoft Exchange Contacts list if the user is
logged on to the Web Client using their directory service account. When the user sends a
document to the Send Email destination, a log on is attempted using the current credentials used
to log on to the Web Client. If those credentials fail authentication, a log on screen appears where
the user can log on to the Microsoft Exchange account.
Note The Contacts search is automatically enabled for the Microsoft Exchange destination, as
explained in the Kofax Front-Office Server Configuration Guide for Microsoft Exchange.
Contacts matching the search criteria and that have data that match the search type (email address
or fax number) will be returned in the results list.
Important For the Contacts list lookup to work, Outlook must be configured with the Microsoft
Exchange Server account type, and Use Cached Exchange Mode must be enabled. Any newly
added Contacts will become available the next time the user’s Outlook client synchronizes with
the Exchange Server.
For example, user Max James logs on to the Web Client using his sAMAccount name mjames, and
clicks the MS Exchange 2003 destination type. If his company’s Microsoft Exchange log on also
uses the sAMAccount name, he will not be prompted for an additional log on. However, if his
company uses the first.last convention for user name, then Max will be prompted to enter his
password and user name max.james to log on to the destination. A Lookup List search would