Troubleshooting for server authentication
Mofiria’s vein authentication can be executed on the device or centrally on a server. However, when you are using server authentication, what if there is something wrong with the data communication or authentication server and the process can’t be done?
Surely it would affect your business greatly. There are many ways to prevent this critical situation such as building a backup server and communication line, introducing a UPS (Uninterruptible Power Supply), introducing a cloud storage and so on. However, there is no perfect solution.
Cache Matching feature
In such case, we recommend using the cache matching feature, also referred to as the offline matching feature.
This feature enables doing offline matching in case the authentication server is unavailable due to some reason. Please note that it is only for 1:1 server authentication.
The steps of cache matching are as follows:
- Store sample data that is succeeded in server authentication.
- Transfer stored cache data to authentication device using Mofiria’s API when offline matching is required.
- Do matching process on device.
- The result returns to the client computer.
You can manage the history of this feature by repeating the steps above for each history.
Supported SDK and Device
This feature is supported by the following client and device controlling SDK:
- MSDK-DCL-02 for Windows 2.2.0 or later
- MSDK-DCL-02 for Mac OS 2.2.2 or later
- MSDK-DCL-02 for Android 2.2.0 or later
- MSDK-DCL-02 for Ubuntu 2.2.1 or later
All of the current authentication devices except Bluetooth connected device FVA-U4BT support this feature. However, some devices other than FVA-U4ST with some older firmware versions don’t.
Please contact us if you are not sure whether or not your device supports it.
Author of this article
Senior Sales Manager
General Manager in Marketing