This would require using the Windows authentication mechanism as a form of encryption, but it could be useful for documents that are shared among a group of users, as you could tie access to AD permissions.
Right now it seems to be very difficult (impossible) but as soon as there's a way to integrate this, we will investigate...
The issue with Windows Hello's authentication API is that it can only be called by the system or UWP apps. RoyalTS would have to completely change it's underlying mechanisms to deal with encryption not to mention convert to a UWP platform.
Best way to implement this would be Windows "hello". It's a new authentication api, that support multiple devices and methodes. It also supports u2f 2-factor authentication ... i've just send you a idea request some minutes ago about u2f/yubikey ;)
Thanks for the explanation. Makes sense!
To be honest, our priorities are elsewhere at the moment but once we have the time and resources, we will definitely look into it.
Synaptic (maker of a large number of the finger print readers on laptops) along with BroadCom have APIs available to developers than can make a direct driver call to the reader. If a plugin could be developed that made that call using their APIs, support for fingerprints could eventually be implemented.
I'm sorry but I don't understand. What is a "synaptic API"?
I did some research a while back but I couldn't find a general API for fingerprint readers. As far as I know, there's nothing built-in in Windows.