Usually the default IE settings are sufficient. 2.) Confirm IE settings are configured correctly: a.
Typically if the ActiveX component of the Online Client software is blocked this demo site will relay such information. Visit o. and click the checkbox to register a print.
Confirm this by going to Control Panel - >Administrative Tools - >Services d. Biometric Authentication Service (c lient 4.x) or DigitalPersona Authentication Service (client 5.x) should be running and set to “automatic”. Online Client 4.x or 5.x should be listed in the Program & Features list in the Control Panel or Add \ Remove Programs c. Fingerprint reader light should be glowing and respond to finger touches (flash). “regsvr32 DPICACnt.dll” Initial Troubleshooting Steps: 1.) Confirm the biometric device and software is configured correctly. WARNING: If Citrix is updated, admin must re - register the component. DPICACnt.dll is the DP Citrix plugin a nd should be located under the “%programfiles% \ Citrix \ ICA Client \ ” folder.
How It Works for Citrix Virtually the same for RDP except the fingerprint data is passed to DPICACnt.dll instead of DPTSClnt.dll.
8.) The web page submits information to the Authentication Service for e nrollment, verification, or update purposes (adding \ removing a registered print).
7.) The Online Client control fires a javascript to relay notification to the browser a finger was captured. 5.) DPTSClnt.dll sends device connection and capture information to the Biometric Authentication Service (BAS) residing on the terminal server (over a virtual channel) 6.) The server side BAS sends the co nnection and capture related data to the Online Client control in the browser. 4.) The Biometric Authentication Service notifies the DPTSClnt.dll (the plugin loaded by mstsc.exe) of the device connection and any other fingerprint related events such as a capture. 3.) The Biometric Authentication Service is notified of the device connection. How It Works for RDP Assuming the Online Client software is installed on both the client machine and the terminal server or remote desktop : 1.) A reader is plug ged into the client machine. 8.) The web page submits information to the Authenticat ion Service for enrollment, verification, or update purposes (adding \ removing a registered print). 6.) A finger event is passed from the Biometric Authentication Service to the Online Client control. 4.) The Online Client control waits for a fingerprint event 5.) User presses his \ her finger.
2.) A driver is loaded by Windows 3.) The Biometric Authentication Service is notified of the device connection. Firewall Biometric Authentication Service \ DigitalPersona Authentication Service How It Works (non RDP or Citrix) Assuming the Online Client is installed and browser has ActiveX enabled the behavior is as such: 1.) A reader is plugged into the client machine (this can be a built - in reader or an external re ader). It is important to understand how the software works in order to troubleshoot. Below is a high level overview of the DigitalPersona Online Client and comm unication path with the authentication server. Troubleshooting Steps: Online Client & Reader End Users The purpose of this guide is to provide sufficient information to DigitalPersona Online providers and partners such that they can be equipped technically to quickly address some of the most common issues encountered by DigitalPersona Online Client end users.