404 Page not found clicking links in the readme.md about digitalpersona-authentication HOT 1 CLOSED

To see documentation with correct links, open it from GitHub Pages, not from the raw Markdown files in the repo.

The service endpoint is one of DigitalPersona Access Management Web Services (DPAM WS) endpoints, providing corresponding APIs. You need DPAM WS installed and properly configured. The @digitalpersona/authentication uses DPAM WS to communicate with DigitalPersona Authentication Server (which is a Win32 service running on AD domain controller) via HTTP.

NOTE: If you do not use DigitalPersona Authentication Server (AD or LDS), you cannot use DPAM WS and, correspondingly, you cannot use the @digitalpersona/authentication library. In this case you'll need to implement your own biometric authentication service, which will do its own fingerprint enrollment/matching using samples collected by the @digitalpersona/devices.

For authentication you need to provide a URL to a Web Authentication Service (WAS), typically it is in a form https://<your web access management host>/DPWebAUTH/DPWebAUTHService.svc.

BTW, the piece of code cited is not quite correct: the input parameter for the FingerprintAuth constructor should be not a URL, but a IAuthService instance, which is a thin DPWebAUTH client wrapper from the @digitalpersona/services dependency. The endpoint URL is a parameter of the AuthService constructor.

You can see a correct example of endpoint configuration and usage in the sample:

• endpoints are defined (see line 17)
• endpoints are used to initialize the IAuthService instance (see line 62)
• IAuthService reference passed to the FingerprintsAuth (see lines 26, 29 and 80).

from digitalpersona-authentication.