c# - Authenticating window user using biometric system connected to LDAP server -



trying build 1 intranet application. trying authenticate user using biometric system, fingerprints precise. in laptops or notebooks have seen there fingerprint authentication system. same thing trying build not particular person. difference person's biometric information stored on ldap server. has right access use particular machine can use after getting authenticated. trying user's biometric information using external biometric device. have gone through few documentations on windows biometric framework. , using sensor adapter , engine adapter plug-ins can user's biometric information , processed , can send server.
query having here is:

  1. first thing first breaking microsoft's policy here achieving this?
  2. if not how can windows system lock , unlock after getting response server whether user valid or not?

has ever tried ?
can me ?
thank in advance.

if you're saying want notify built in windows login / authentication system (known system credential provider) user authenticated this not supported official windows api. if supported create malware notified api user authenticated / authorized, thereby rendering of windows security meaningless. should grateful not officially supported.

trying implement without official api support against terms of use. since not officially supported, have resort awful hacks work, implementation of considered either reverse engineering kernel or hacking kernel (or both) microsoft's legal team. if believed wrong... want fight them (and deep pockets)?

let's consider if no official unlock api exists, required use kind of backdoor achieve it. if such thing exists, subject being rendered useless ms update (which nuke app's login implementation).

now fire , fury out of way, let me state not lost, provided targeting more recent version of windows.

you can implement own biometric security system described. known third party credential provider separate system, , microsoft recommends require users setup system credential provider fallback in case third party credential system fails reason. if not, user account impossible recover. again, key difference first example system separate , distinct system credential provider (windows native lock screen).

i stress though, implementing third party credential system still far trivial. want read extensively on proper interfaces have implement. i'd recommend starting here:

https://msdn.microsoft.com/en-us/library/windows/desktop/mt158211%28v=vs.85%29.aspx?f=255&mspperror=-2147217396

there apparently sample located in windows sdk installation directory under \samples\security\credentialprovider. also, there nice technical reference of credential providers located here:

https://msdn.microsoft.com/en-us/library/windows/desktop/bb648647%28v=vs.85%29.aspx?f=255&mspperror=-2147217396

click link says "credential provider driven windows logon experience" download tech document.


Comments

Popular posts from this blog

python - Operations inside variables -

Generic Map Parameter java -

arrays - What causes a java.lang.ArrayIndexOutOfBoundsException and how do I prevent it? -