05. Training – Part 2 [4:49]
Description: This video explains the following:
How to upload all fingerprints.
How to identify and verify users.
0:00 An important function that we haven’t talked about till now, is upload fingerprints. So let’s assume that you are keeping an HR Database here of users and fingerprints. Obviously you want to store those in FileMaker for retrieval later on and for use throughout the network and throughout the system. Naturally you’d want to protect this file at all cost because this is where the fingerprint digital data is stored; although it is encrypted here, you don’t want users to have access to that for manipulation and so forth. So you’ll want to protect that in a way that makes sense for you in your system. But once those fingerprints are in FileMaker; and you quit FileMaker, those fingerprints are not available anywhere on the device or within the software; it’s been completely been removed and the only way to get them back into the device in preparation for the identification process is that you have to upload them. So let’s take a look at that script.
1:05 What this will do is it will go to the layout where the fingerprints are stored and show all records; we get a quick count and then we go back after that count was successful. If the count is zero; this just means we have no fingerprints to upload; this is just preliminary standard FileMaker logic. If there are fingerprints, we’ll create a new window and we’ll go to the layout where the fingerprints are stored, show all the records starting with the first record and begin to upload those to the device. Let’s take a look at what that looks like; the actual command is “AddFingerprintToUser”, and what you’re going to give it is the fingerprint User ID and the actual fingerprint container data that we stored earlier when we enrolled; and the finger index in which to store that container data or that fingerprint data. So this literally uploads the fingerprints to the device; and we’re going through all the records and doing that in this manner through a standard loop. So that’s uploading fingerprints and once they’re uploaded the system is ready to identify.
2:16 So the Identify process is really where you got to choose what you allow and what you don’t allow. The purpose of this solution is to simply identify that that person is who they say they are and it does it by way of their fingerprint. So let’s take a look at the identify script and this one incidentally is one of the simplest of all. We simply set the value in a variable and call the PCFP_Identify function and determine if it is a pass or fail. If it’s a fail we return an error, if it’s a pass we let them do whatever they need to do. In this case in the demo, we’re showing an unlock icon as a result of a pass; meaning we’ve identified you; you can now have access to the information. So the logic that you’ll use is going to be under this section here; which says what do I want to validate, what do I want to verify and allow; and that really is the sky is the limit. So here is a script too that will be highly protected in a solution where you wouldn’t want people to be able to play with the identify script as a result of what it’s going to allow. One important note about the Identify function is that there is actually a parameter that you can user here; we don’t use it in the demo, but certainly one you can use.
3:39 And (we’ll put it down here for clarification), Optional Print Count. This allows you to specify how many fingers you need to identify before allowing that user in. So let’s say for example that a user has enrolled all ten fingers; you may want to require two or more fingers in order to properly and definitively identify that user. So for example; we can say we want to identify this user by requiring four fingerprint scans, successful scans, before allowing the pass/fail; before allowing them rights. In most cases PCFP_Identify and a single fingerprint, which is the default, is good enough.
And that’s a look under the hood of the Biometric Fingerprint Reader.