I want to create an android online voting system app. This app will use Samsung fingerprint scanner to verify voter identity - valid or not - on our server. Is it possible for Samsung fingerprint scanner SDK to verify the fingerprint by checking on our server rather than the android SQLite database?
Samsung provide a Pass SDK
Pass SDK allows you to use fingerprint recognition features in your
application. With Pass SDK, you can provide reinforced security, since
you can identify whether the current user actually is the authentic
owner of the device.
If you want to get fingerprint (template or image), it's not possible with Samsung device. You could only check owner of device.
Related
I'm trying to enroll a device with the Android Device Policy app. I created a enrollment token, and typed it into the app. The app says it's going to encrypt the device. I want to skip the encryption, but it is not allowed. Is there any solution for that? Why is it mandatory to encrypt the device?
Edit:
The device is a Lollipop(Android 5.1) one. There is no camera or NFC on it.
Im developping an application with android studio, the application is for attendance using fingerprint and I want be able to register fingerprint of users using a desktop application and the fingerprint will be registered from a physical fingerprint reader, data encrypted from it will be stored in a Mysql database. So I want users to use their android phone with fingerprint sensor to respond the attendance. Actually I dont know if it is possible to compare encrypted fingerprint from android phone and for this coming from the physical fingerprint reader.
What I need is just ideas on encryption or comparison between those two sources of data.
Thank you
From what I can understand is that you are trying to develop an application with two ends.
One for the fingerprint enrollment from a desktop application.
One for matching the fingerprint to a probe fingerprint of an individual from an Android Device.
See what you are trying to achieve is a bit nearly impossible as #Michael clearly stated.
The answer is a bit elaborated. (The boring but detailed stuff)
For the enrollment part, if you are using a physical fingerprint reader, that device will definitely provide you with a fingerprint image along with some ISO templates of the fingerprint whose name shall be kept unique by you and it's name can be stored in the Database. Let's call this ISO as gallery ISO.
For the verification part, there are two approaches.
1:1 fingerprint match(the person first claims to be someone and places his/her fingerprint on a verification device to confirm the claim) and 1:N fingerprint match (the person doesn't tell your verification system who is he/she, but simply places his/her fingerprint on the device and the system searches for a probable fingerprint match)
Android devices store a fingerprint which cannot be accessed by the API, all you can achieve is that either a YES or NO. That the fingerprint is enrolled in the device or not.
You will have to use the same physical scanner connected to an USB OTG to the android device, if the physical scanner provides the SDK to support android device then it's fine else you cannot just have the same ISO template from any other scanner.
However there is a standard template and most of the scanners generate it.
Like ISO-19794-2/FMR
The ISO generated at the verification end shall be called a (PROBE ISO).
Your fingerprint scanner's SDK shall really provide you a function like below:
long score = CompareISOs(byte[] GalleryISO,byte[] ProbeISO);
The "score" gives out a value which tells you how much confidence is the scanner that the two ISO templates are same and SDK must also provide you with a threshold like say 800.
so if score anytime after comparison is greater than 800. You have a match.
This is 1:1 verification.
one-to-n is a way more hectic task and requires much complex SDK like ABIS. That I shall leave as a research topic for you.
I hope my answer helps you to some level. I came along this question and decided to reply because you genuinely asked for some ideas. I hope this helps you to kick start your research on fingerprints.
Kudos!
I want to build an android app in which the attendance of the person can be viewed when the person touches the fingerprint reader. The fingerprint reader would be placed outside every classroom in the college. Is this possible through android app? If not possible through fingerprint, then kindly suggest any other alternative through android app.
This would not be possible directly using the fingerprint scanner on an Android device, as the fingerprint data is stored securely on the device, and not available to any applications. The Fingerprint Authentication API only provides whether or not a fingerprint registered on the device was touched to the scanner, it does not differentiate between individual fingerprints.
You should be able to use a third-party fingerprint scanner that connects to an Android device and does differentiate between individual fingerprints. A quick search lead me to the U.are.U SDK for Android, which seems to provide this functionality for their products.
Another option is to use a third-party mag-stripe card reader (provided the students have an ID card with a mag-stripe) that connects to an Android device, of which a variety of options are available.
I want to record customer data including fingerprint via android tablet in banking project. When customer deposit or withdrawal money, will verify which customer by finger print data. Android device record fingerprint data and sync with webserver (asp.net). So, What is the best way to develop for fingerprint verification? If fingerprint device connect with android tablet is more easy, please suggest me.
Take a look at FingerprintManager whic was added in API 23 (Android 6). https://developer.android.com/reference/android/hardware/fingerprint/FingerprintManager.html
Also there is a demo project located here: https://github.com/googlesamples/android-FingerprintDialog
Please start by reading this : https://en.wikipedia.org/wiki/Fingerprint_recognition.
There's some fingerprint scanners compatible with Android Platform and with SDK for Android. Scanners are plugged on USB port so you can't charge tablet and use fingerprint scanner simultaneous. For instance:
http://www.dermalog.com/en/products_solutions/fingerprintscanner/
http://www.futronic-tech.com/product_fs80h.html
http://www.crossmatch.com/authentication-hardware/
There's also some devices with integrated fingerprint scanner and with SDK to get fingerprint image or template. For instance Samsung or iPhone only provide SDK to verify 1 user (user of device) but others manufacturers provide a SDK to get fingerprint image or template.
If you want to match user on server (fingerprint data of users are stored on server) you have to use an AFIS solution https://en.wikipedia.org/wiki/Automated_fingerprint_identification.
Here some providers of AFIS solution:
http://www.neurotechnology.com/megamatcher.html
http://au.nec.com/en_AU/solutions/security-and-public-safety/biometrics/afis-fingerprint-identification-features.html
http://www.innovatrics.com/products
http://www.dermalog.com/en/products_solutions/afis/
http://www.m2sys.com/automated-fingerprint-identification-system-afis/
I would like to build an enterprise application. So in these case. i want remotely manage my Android Device,
Example. I want to disable USB port my office users device & New application installation. Since device will be provided by us , So in order to main security.
How to achieve this. Did Google Provides any APIS
From the Dev Guide:
http://developer.android.com/guide/topics/admin/device-admin.html
Android 2.2 provides a Device Administration API that allows you to set certain policies for the device on which your app gets installed. There is also a step-by-step tutorial on the same page.
This API has been used in some of the existing apps that come bundled with the Android source code. For eg: Exchange Email.
The Device Administration API only supports certainpolicies. If you need to restrict the use of the device, it might also be a good idea to tie in your app with the Exchange Email (or a corporate account, since you mentioned it's for office users). A typical corporate Exchange account has a much larger policy set.