aXsGUARD Identifier 3.0.2.0 Product Guide v1.5
User Authentication Process
This setup is achieved by configuring the following Policy options:
Local authentication:
DIGIPASS
or
DIGIPASS/Password
Back-end authentication:
Always
Back-end authentication protocol:
RADIUS
Password autolearn:
On
Stored Password Proxy:
On
Image 13: Steps in the Retrieval of RADIUS Attributes
3.6.4
Back-end Server Records
If a back-end server is to be used by the aXsGUARD Identifier for authentication, it must be registered in the
aXsGUARD Identifier. It is possible to create more than one back-end server record, for fail-over purposes. You can
also allocate different back-end servers for different user domains.
3.6.4.1
Fail-over Strategy
Each back-end server record is assigned a
Priority
. This comes into effect when multiple back-end servers are
available, and the aXsGUARD Identifier must decide which to use for a back-end authentication request. The
aXsGUARD Identifier attempts to connect to the back-end server with the highest Priority rating. If it is not available
after the set
No. of Retries
, the aXsGUARD Identifier attempts to connect to the back-end server with the next
highest Priority rating.
©
2009 VASCO Data Security
44
