aXsGUARD Identifier 3.0.2.0 Product Guide v1.5
Client Components
Caution
Modifying the IP address of the aXsGUARD Identifier in the Configuration Tool, results in the
creation of a new administration program client component record. The older records can be
erased: however, do not erase the client component configured for the current IP address,
because this prevents access to the Administration Web interface.
18.3
Component Lookup and Verification
The component making a request 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 according to the type of component, as outlined below.
18.3.1
RADIUS Client
The RADIUS protocol can support three services (RADIUS AAA):
RADIUS Authentication is supported by the aXsGUARD Identifier (described in section
RADIUS Accounting is is supported by the aXsGUARD Identifier. With a RADIUS back-end server, Accounting
requests are forwarded to the back-end server and handled by proxy. Without back-end authentication, audit
messages are generated.
RADIUS Authorization handles requests for an authentication client to use a particular service and is only
possible with a RADIUS back-end server. RADIUS Authorization cannot be supported by the aXsGUARD
Identifier without a RADIUS back-end server.
A RADIUS Client Component record is required for clients sending authentication requests to the aXsGUARD
Identifier
using the RADIUS protocol.
For a RADIUS Client, the following component checks are made:
Component Record exists
A Component record for the RADIUS Client must exist, otherwise the request is discarded without responding:
Type = RADIUS Client
Location = the source IP address of the request
OR if there is no RADIUS client at the specified location, Location = default
Shared Secret is set
The Component record must have a Shared Secret value set, otherwise the request is discarded without
responding.
©
2009 VASCO Data Security
117