aXsGUARD Identifier 3.0.2.0 Product Guide v1.5
DIGIPASS
Example
Time window may be 5 steps in either direction.
This means that 11 OTPs would be considered valid – the exact OTP for that time, and the OTPs for the 5 time steps either side of the
exact time. If the OTP given is for a different time step, the time shift for that DIGIPASS device is recorded. The next time the User logs
in, the expected OTP is calculated based on the time shift.
Last Event Value (usage information):
the current number of uses of the DIGIPASS Application, according to
the DIGIPASS device. This can get out of sync with the number of uses recorded by the aXsGUARD Identifier
when:
login failures occur for other reasons than incorrect OTP
the DIGIPASS device has been used without a login (e.g. children have been playing with it)
the DIGIPASS device is being used to log in to two separate systems
The purpose of this setting is much the same as the Last Time Shift setting – it allows the aXsGUARD Identifier to
track any shifts between the event count recorded by itself and the DIGIPASS device.
17.4
DIGIPASS Assignment Options
DIGIPASS Records may be assigned to Users in a number of ways, depending on the requirements of your
company. For example, a company with only a few User Accounts may use Manual Assignment. A larger company
needing to distribute large numbers of DIGIPASS devices may find it easier to simply distribute them and request
Users to go through Self-Assignment or Auto assignment.
For more information on DIGIPASS assignment throughout your organizational structure (with domains and
organizational units) and the restrictions, please see section
Note
DIGIPASS records must be imported into the data store before being assigned to Users.
©
2009 VASCO Data Security
106
