Identifying internal and linked users, Internal users, Linked users – Kofax Front-Office Server 3.0 User Manual
Page 14: Linked users from non-default domains

Kofax Front-Office Server Administrator’s Guide
14
Kofax, Inc.
#type=ActiveDirectory
or
#type=Ldap
b
Uncomment the property:
type=None
2
Save the file.
3
Stop and restart Kofax Front-Office Server.
Identifying Internal and Linked Users
In the Administration Console, you can add internal users whose data is stored in the embedded
database, and you can also link users from a directory service. For example, for Active Directory, a
user can come from the default, child, or trusted domains. For LDAP connections, the list of
external users is based on how you configured the conf\avalin_security.properties file.
All users are identified and authenticated based on the following:
In the Administration Console and the Web Client and MFP log on: domain (optional),
user name, password
At the MFP for Send to KFS Inbox: domain (optional) and user name
Internal Users
Internal users are not associated with a domain, so any user name that does not include the
domain will be checked against internal users first.
Linked Users
Linked users from the default domain can omit the domain when logging on to the
Administration Console, the Web Client, or when sending to KFS Inbox from an MFP. For
example, user DefaultDomain\mjames can log on simply as mjames.
Special Case: When User Name and Password are the Same
If a linked user on the default domain is also an internal user with the same password, and the
domain is not included in the log on, the internal user will always be used. To be recognized as the
linked user, the log on would have to include the domain, such as DefaultDomain/mjames.
Note
For LDAP connections, the domain name “external” is used, so the log on would be
external\mjames
Linked Users from Non-Default Domains
For linked users on the non-default domains (child or trusted), the domain must always be
included as part of the user name.