aXsGUARD Identifier 3.0.2.0 Product Guide v1.5
Client Components
18
Client Components
18.1
Overview
Each application in the network which needs to access aXsGUARD Identifier services, must be registered on the
aXsGUARD Identifier as a client component for access to be allowed. Client component registration also specifies
the applicable policy for handling a request. More information regarding client component and policy verification
during an authentication attempt is available in section
The Administration Web Interface allows you to create, manage, and delete Client Records, and allows the
assignment of:
Permissions for authentication requests from a client to be handled
Policies to be assigned to authentication requests
Secrets to be shared between RADIUS Clients and the aXsGUARD Identifier
In this section, we describe the client components necessary for the administration program, the RADIUS client and
the IIS module.
We strongly recommend that you read section
first, to better understand client component use.
18.2
Standard Component Properties
Four properties common to all client components are:
Application type (explained below)
Location: the source of the request
Protocol: communication protocol to use (see section
Policy: the applicable policy for handling a request (see section
There are six client application types which interact with the aXsGUARD Identifier:
RADIUS Authentication
IIS Authentication
Administration Program: an administration program client component record is added by default for the
Administration Web Interface. This component record includes a policy to allow connections from this program.
SOAP Authentication (currently in development, to be included in a future release)
DIGIPASS Software Provisioning (currently in development, to be included in a future release)
Electronic Signature Validation (currently in development, to be included in a future release)
©
2009 VASCO Data Security
116
