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

Asked

Viewed 1,386 times

1

Galley,

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

The Webforms page is called from iframe within certain views, that at certain times step the identification of the user that needs to be identified in a 1x1 comparison, or do not pass any parameter when it is 1xN.

Right, when I made the application available for external access, and connected the biometric reader on the computer that accessed, 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 cooperation.

javascript c# asp.net-mvc web-application webforms
  • 1

    You just found out that web application only serves some. Some works by leaps and bounds, although those who developed it think it’s great, others can not function. The solution is not to use a web application.

  • What is the biometric reader model? Which SDK does it use?

  • @The biometric reader is fultronic fs80h, and I use the neurotech megamatcher sdk.

2 answers

1

Any suggestions on how I can do this?

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

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

Therefore, 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.

0

Hello,

Its 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 the local resources of the computer, unless the user installs a plugin.

The bad thing about 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 as you already did on the server, and will publish a REST service that will be consumed by your page through Javascript.

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

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

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

Browser other questions tagged javascript c# asp.net-mvc web-application webforms

You are not signed in. Login or sign up in order to post.