aXsGUARD Identifier 3.0.2.0 Product Guide v1.5
User Authentication Process
3.2
Identifying the Component Record
A record must exist in the database for any client application sending an authentication request to the aXsGUARD
Identifier. This client component is identified using:
Component Type – A fixed name such as RADIUS Client, Citrix Web Interface, Outlook Web Access or
Administration Program
Location – the source IP address of the request
The component lookup and verification processes vary slightly according to the type of component. For more
information please see section
3.3
Identifying a Policy
Policies specify various settings that affect all request handling processes. Each request is handled according to a
Policy, which is identified by the applicable server and client records (see also sections
Client Components respectively).
For more information on Policies, please see section
For a full listing of possible Policy settings and the pre-loaded policies available with the aXsGUARD Identifier,
please refer to the
aXsGUARD Identifier Administration Reference Guide
.
3.4
DIGIPASS User Account Lookup and Checks
3.4.1
Overview
aXsGUARD Identifier performs a number of checks before proceeding to local authentication, including:
User ID and Domain Resolution, which is explained in section
DIGIPASS User Account Lookup, which is explained in section
Checking whether
Dynamic User Registration
is enabled for a user (if a DIGIPASS user account doesn't exist),
which is explained in section
3.4.2
User ID and Domain Resolution
Caution
Using NT4-style domain qualification in front of the User ID:
DOMAIN\userid
is not allowed on the
aXsGUARD Identifier.
©
2009 VASCO Data Security
26
