Please implement Native messaging mechanism! Internet Banking users are used to sign their contracts via a smart card (which uses WinCrypt API). Nowadays, after deprecation of applets, there is no other way to access Windows API and use a smart card in order to make a trusted digital signature.
This works okey. Connects to backend on windows load event. Tested on 15025.rs_prerelease
Finally I was able to make working Edge Native Messaging Host UWP app but with one serious issue!
UWP app starts only after some user action in the browser (like nagivated to the page and page loaded, tab switched, clicked on the extension icon, etc.). Before this UWP app doesn't started even I call chrome.runtime.connectNative() or chrome.runtime.sendNativeMessage(). Also UWP app started immediately right after extension debugger opened. What is the reason of this issue?
I got error launching the Edge Native Messaging Host UWP app from the extension, details are here:
Could someone tell me what's the reason UWP is not started?
Francisco de la Peña commented
This is not really needed for privileged stuff, I do digital signature with the following:
1: Create a desktop privileged app with HTTPS service listening in some port.
2: Create a custom local-only host and add it to the HOSTS file pointing to 127.0.0.1 and ::1.
3: Create a generated CA (generated in the installer for *every* machine).
4: Create a server cert for that local custom domain signed with that CA.
5: remove the CA private key.
6: Add the CA cert to the system trust with certutil or whatever.
7: Use the server cert and key in the SSL server and serve on that domain and port.
8: With XmlHTTPRequest, call that local domain from the web site to that specific port and some path, e.g. a POST request.
9 The local service should trigger something and return data to the server after asking something to the user. This is the way the NexU app included in the DSS project work.
I need it for sign PDF files via plugin and native app.
John D. commented
Native messaging is required to communicate with a separate process for support of speech recognition in Edge.
We need native messaging to interact with a piece of security code that cannot be executed in the browser's context.
This is very important api.We are not able to support edge because this api is missing.
We are unable to provide an extension for Microsoft Edge unless is supports Native Messaging.
Norton needs this for program development.
alessandro ciurlo commented
Our company use connectnative to exchanging data from internet browser to our external desktop application. We support Chrome Opera Firefox and with BHO technology Internet Explorer but there is no way to support Microsoft Edge. if connect native is not supported
waiting for native messaging support. Is there a plan?
waiting for it to support Edge for our users
Roman Alexandrov commented
Our company is developing a password management software. We support all major browsers right now: Firefox, Chrome, IE and Safari. Alas, we can't implement proper web extension for Edge when there is no way to communicate to the native API. Implementing Native Messaging in Edge will allow more users to start using it right away.
Nate Chen commented
Absolutely critical to me too.
Seems that Firefox has this implemented in v50.
Relying on a smart card reader attached to a pc is not realistic anymore. How can visitors use your website on mobile devices?
In Belgium, all financial institutions have switched to a separate card reader for authentication: http://blogimages.seniorennet.be/themafotos_20/28-63a49029d02d19be50388790d51282cc.jpg
Yann RAOUL commented
Absolutely critical to me too. We need that implementation for our customers who will use Edge and our site.