It just needs couple of mins to setup the client-server setup with establishing the communication to fingerprint scanner.
Templates and additional information are transferred with 5 layer encryption protection which makes the data most secured and unbreakable to the intruders. More details are shared in the below documentation.
Who wants to read this page?
This page is applicable for people who falls in the following requirements
If you are looking for fingerprint scanner to read the fingerprint from your website
If you are looking for fingerprint web site login
If you are looking for fingerprint attendance system at your website
How to do the setup?
Now setup is ready, you can right way start using the fingerprint scanner and use it for your login page or attendance page or any other purposes.
How it works
The following diagram explains the functional components involved in the overall communication and their possible communication messages between components.
On the successful completion of any operation, the respective server URLs, if configured, will be called or the events to be triggered with its resulted data. Following are the operations and its result data.
Capture - Encrypted fingerprint template, bmp base64 fingerprint image, encrypted capture time at client system, encrypted auth token
Merge - Encrypted fingerprint template of given three fingerprint templates, encrypted merged time, encrypted auth token
Compare - Encrypted score, encrypted comparison time, encrypted auth token
CaptureAndVerify - Encrypted fingerprint template on success or decryption-failable random string, encrypted capture time at client system, encrypted auth token
Web API or Online SDK for fingerprint reader
HTML Page Change
In client html page, the following code should be included as the first script section in the head section.
fp.onCaptureSuccess = null;
fp.captureReturnImage = false; // By default only template is captured, setting it to true returns BMP image along with template.
fp.onMergeSuccessUrl = null;
fp.onMergeSuccess = null; // if onMergeSuccessUrl is not set, the function assigned here will be triggered
fp.onCompareSuccessUrl = null;
fp.onCompareSuccess = null; // if onCompareSuccessUrl is not set, the function assigned here will be triggered
fp.onCaptureAndVeifySuccessUrl = null;
fp.onCaptureAndVeifySuccess = null; // if onCaptureAndVeifySuccessUrl is not set, the function assigned here will be triggered
fp.onCaptureFailure = null;
fp.onMergeFailure = null;
fp.onCompareFailure = null;
fp.onCaptureAndVeifyFailure = null;
Call triggerCapture( sendImage ) which takes care of capturing the fingerprint templates and images. Once successful capture, it triggers the fp.onCaptureSuccess call. On failure, it triggers fp.onCaptureFailure. Sending true for sendImage will and capture the fingerprint image and pass into the onCaptureSuccess event.
A function as below to be written to handle the capture data and the same function name should be assigned to fp.onCaptureSuccess;
function handleCapture(template, image)
// template is the encrypted fingerprint template
// image is base64 bmp image. You can use this data to display the fingerprint image on the browser
Call tiggerMerge( tmp1, tmpl2, tmpl3) which merges the three templates into one. On successful merge, the template will be passed to the URL configured in fp.onMergeSuccessURL. If it is null, then fp.onMergeSuccess event will be triggered.
A function as below can be written to handle the merge data and the same function name should be assigned to fp.onMergeSuccess. Note that this is an optional operation.
// template is the encrypted merged template of three fingerprint templates
Call tiggerCompare( tmp1, tmpl2) which compares the two templates and sends comparison score. The comparison value can be anything between 0 and 100. On successful comparison, the score will be passed to the URL configured in fp.onCompareSuccessURL. If it is null, then fp.onCompareSuccess event will be triggered.
A function as below can be written to handle the comparison result and the same function name should be assigned to fp.onCompareSuccess. Note that this is an optional operation.
// the comparison score will be between 0 and 100.
Call tiggerMerge( tmpl ) which captures new fingerprint, compares with the passed one and sends the response to fp.onCaptureAndVeifySuccessUrl. This operation shall be used for fingerprint login purposes. If onCaptureAndVeifySuccessUrl is null then fp.onCaptureAndVeifySuccess event will be triggered.
A function as below can be written to handle the merge data and the same function name should be assigned to fp.onCaptureAndVeifySuccess. Note that this is an optional operation.
// the score of the comparison of newly captured template and the passed one will coming between 0 and 100.
CAMS ensures that the complete system is highly secured and the data getting transferred are not breakable. It establishes the Industrial standard Trusted Path and Trusted Channel. Following are the few primary security aspects implemented in our system.
All the data which includes fingerprint template, comparison score, success/failure status, auth token, operation time are fully encrypted by Advanced Encryption Standard (AES-256) algorithm
All the operations sends the encrypted auth token and the operation time. This enables you to validate if the data is new or something manipulated with older data
Communication between scanner handler and cams security server happens through HTTPS
The data gets transferred between scanner handler and the cams security server are five layer encryption applied with (1) date are randomly bitwise rotated/altered, (2) rotated/altered data are encrypted with internal encryption algorithm and (3) and on top of the encrypted algorithm AES-256 encryption algorithm is applied. This ensures that data are impossible to break, (4) and (5) are confidential
Clients are strongly recommended to implement your site with SSL. This ensures that eavesdropping becomes to complex
As we ensure various security measures are handled, the data are completely safe till it lands to your server.
The fingerprint matching ratio is 1:1 at client level. The mathcing is done with fingerprint templates. We offer 1:N matching with server level which is a seperate feature from this suite. This matching shall be done with fingerprint images.
The present version support all the versions of Windows OS which includes Windows XP, Windows Vista, Windows Server 2003, Windows Server 2008, Windows 7, Windows 8, Windows Server 2012, Windows 10, Windows Server 2016, and any latest windows OS
Various customization and the upgradation may be required from client to client. We list the cost of the common features that requires for every one.
The scanner license are yearly based. Every scanner is required a license which needs to be renewed every year. The windows service handler can be installed in multiple machines and as long as a scanner is having valid license, it can be connect to any no. of computers. It means, that license if scanner only. So, you can use one scanner to multiple computers one after one. The license expired scanner does not return the captured templates.