User's Manual

26
The user is NOT authenticated.
INVALID_BLOB The datum supplied as Blob is invalid. The data in the Blob are both encrypted
and validated. Every variation not carried out by the SDK is identified and
makes the Blob unserviceable.
In that case it is necessary to reset a valid Blob in the database.
It is also possible that an incorrect Blob-key is being used.
The user is NOT authenticated.
INVALID_PACKET The received packet is invalid. Probably it is a transmission error or a
fraudulent access attempt without using a real device.
In this case the user needs to be required to retry and carry out the
authentication.
It is also possible that an incorrect Server-key is being used.
The user is NOT authenticated.
INVALID_COUNTER_REUSE The received packet had already been used previously. Probably it is a
fraudulent access attempt through the reuse of authentication codes that were
previously used and stolen someway.
In this case the user needs to be required to retry and carry out the
authentication.
The user is NOT authenticated.
INVALID_COUNTER_OVERRUN The received packet contains an event counter field with an extremely high
leap ahead It is probably a damaged device or a device that has undergone a
brute force attack attempt.
In this case the damaged device must be replaces, or the counter field must be
reset by using the dedicated function. The user cannot authenticate until the
problem is solved.
The user is NOT authenticated.
INVALID_TIME_REUSE The received packet had already been used previously. It is probably a
fraudulent access attempt.
In this case the user needs to be required to retry and carry out the
authentication.
It is also possible that the clock used for authentication is not correct.
The user is NOT authenticated.
INVALID_TIME_OVERRUN The received packet contains a time field with an extremely high leap ahead.
It is probably a damaged device.
In this case the damaged device needs to the replaced. The user cannot
authenticate until the problem is solved.
It is also possible that the clock used for authentication is not correct.
The user is NOT authenticated.
INVALID_TIME_NOBATTERY The device results authenticated except for the time comparison which is not
available due to the flat battery.
In this case the device must be replaces or considered to all effect as an event-
based device and no more as a time-based device.
The user can be considered authenticated or not at discretion.
INVALID_TIME_LATE The authentication has failed because too long time has elapsed between the
first and the second authentication step. It is probably a user error.
In this case the user needs to be required to retry and carry out the
authentication.