5.5 Fingerprint Related Issues

You can browse the following URL and place your finger on the reader to troubleshoot the fingerprint related issues:

https://127.0.0.1:8442/api/v1/fingerprint/capture

The service returns the response in the following format:

{"BitsPerPixel":x,"BytesPerLine":xxx,"Dpi":xxx,"Height":xxx,"Image":"<fingerprintdata>","Width":xxx,"captureStatus":"Ok"}.

For example: {"BitsPerPixel":8,"BytesPerLine":256,"Dpi":508,"Height":360,"Image":"<fingerprintdata>","Width":256,"captureStatus":"Ok"}.

The following table describes the different parameters of the response:

Parameter

Description

captureStatus

Indicates status of capture. Possible values are:

  • Ok

  • Timeout

  • Error

  • NoReader

Width, Height

Fingerprint image size (width and height) in pixels.

Dpi

Dots per inch. This is used while matching the fingerprint.

BitsPerPixel

Bits per pixel. Typically 6 bits.

BytesPerLine

Bytes per line in image.

Image

Fingerprint image encoded using the Base-64 format in gray scale.

This section contains the following fingerprint issue:

  • Mismatch Error After Migrating from Advanced Authentication 5.6 to 6.0

  • The Nitgen Device Stops Working When It Is Reconnected to a Workstation

5.5.1 Mismatch Error After Migrating from Advanced Authentication 5.6 to 6.0

Issue: After migrating from Advanced Authentication 5.6 to 6.0, while authenticating with the SecuGen Hamster Pro 20 fingerprint reader an error message Mismatch is displayed on Windows operating system.

Workaround: Perform the following steps:

  1. Open the configuration file C:\ProgramData\NetIQ\Device Service\config.properties.

  2. Add the parameter fingerprint.nbisEnabled=false.

    The default value is true.

  3. Save the changes.

  4. Restart the Device Service.

5.5.2 The Nitgen Device Stops Working When It Is Reconnected to a Workstation

Issue: While enrolling or authenticating with the Nitgen eNBioScan-C1 device if you disconnect the device from a workstation and then reconnect, the device stops workind. Also, the workstation does not detect the device.

Workaround: Restart the workstation after you reconnect the device.