Access biometric reader on client side - ASP.NET MVC - WEBFORMS

Question

Access biometric reader on client side - ASP.NET MVC - WEBFORMS

Navigation

#1 by (1 votes)
#2 by (0 votes)

1

Galera,

I developed an ASP.NET MVC application, using a webforms page, in which it is called inside an MVC page. Because only from it I was able to load the DLLs of the SDK, to send requests to a biometric reader, to capture and to authenticate the biometrics.

The Webforms page is called from the iFrame within certain views, which at some point passes the user ID that needs to be identified in a 1x1 comparison, or no parameter is passed when it is 1xN.

Right, when I made the application available for external access, and I connected the biometric reader to the computer that accessed it, the application does not search the reader on the client side, but on the server side. And I need her to look on the client side. Any suggestions on how I can do this?

Thank you in advance, any collaboration.

javascript c# asp.net-mvc webforms

asked by anonymous 15.05.2017 / 01:32

2 answers

Div entire screen with Bootstrap? Loss of Collection of a View Model for the Controller [closed]

score 1 · Answer 1

Any suggestions on how I can do this?

Yes, developing an extension for Google Chrome , or to Firefox , or to other browsers you want.

The problem is that your biometric reader stays on the client and your application is Web, so it stays on the server. They are not the same machine.

So you will have to develop a communication between your plugin and your application developed in ASP.NET MVC. A good way can be this article .

score 0 · Answer 2

Hello,

Your application is web and the biometric reader is on the client machine, so you need to communicate with the hardware through the browser, ie your web pages. The problem is that, for security reasons, browsers prevent a page from accessing local computer resources, unless the user installs a plugin.

The bad of the plugin is that you will need to develop one for each browser, the output for this is to develop a small WindowsService application that publishes a REST service, your WindowsService will do all the communication with the hardware, just like you already did on the server, and will publish a REST service that will be consumed by your page through Javascript.

The request of your javascript will always be for LOCALHOST, since the request will always be for the service on the local machine where the reader will be installed.

One tip, you will need to configure CORS to make the request for LOCALHOST.

I've done it this way and it works great!