Biometric Integration Overview


Overview

Each biometric reader integration differs in its functionality within Access It! Universal.NET. This article should be used to reference the general outline of each integration. Refer to each readers specific knowledge base article for specifics on the reader's configuration and setup.

Access It! Universal.NET Licensing
The following licensing option must be enabled within the Access It! Universal dongle and is a system wide license.

  • Biometric Support - Yes

Suprema (via BioConnect)

Supported Models

A list of supported models can be found within the BioConnect Site.

Enrollment

Enrollment is performed at the card level. If a cardholder has multiple cards assigned, they only need to have their biometric template enrolled once. Within the BioConnect software, only one of their cards can be marked as the "Biometric Card" which the reader will output as the card number once a valid finger is presented.

Association

When enrolling, the card number is used to associate records in the BioConnect software to the card within Access It! Universal.NET. Because the facility code is not used, duplicate card numbers are not allowed. When making modifications to the cardholder or to the card itself, those changes are associated by the respective CardholderID and CardID fields. This allows for changing the card number of an existing card and not needing to re-enroll a biometric template.

Synchronization

Upon initial installation of the BioConnect integration software, an initial synchronization is performed to populate all cards from Access It! Universal.NET into the BioConnect database. Records existing in the BioConnect database are not erased.

Each time the BioConnect service is started, synchronization occurs between the databases. Records existing in the BioConnect database are not erased.

Each time the User Management screen is entered within BioConnect, synchronization occurs between the databases. Records existing in the BioConnect database are not erased.

More Information

Each time the BioConnect software launches, a user name and password must be entered. This can be circumvented when using a domain environment and configuring the domain credentials within the BioConnect software. Specifics on configuring this reader within Access It! Universal.NET can be found in the  Suprema BioConnect Integration article.

Suprema (via OSDP)

Supported Models

BioEntry W min f/w 1.1_150409

All Suprema version 2 products

Enrollment

Enrollment is performed at the Cardholder level. If a cardholder has multiple cards assigned, they only need to have their biometric template enrolled once.

Association

Due to the integration being reliant on Mercury-Security, the association between the biometric record and the card is handled by the SCP controller and transparent within the software. Upon a card presentation, the SCP controller confirms if the reader requires biometric verification, loads up the cardholders template, and prompts the biometric reader to begin looking for a card. If the template matches then access is granted.

Synchronization

Biometric templates are saved in the SCP controller each time the cardholder or card is saved within Access It! Universal.NET.

More Information

Because this integration requires a card to be swiped prior to presenting a fingerprint, it is not possible to achieve a finger-only solution. This solution is idela for replacing legacy biometric installations. For a new installation, it is recommended the Suprema (BioConnect) solution be used. Specific information on configuring these readers within Access It! Universal.NET can be found in:

Suprema OSDP Reader

ZKAccess (via ZKBioPack)

Supported Models

  • MB700
  • TF1700
  • F18
  • FV350

Enrollment

Enrollment is performed at the card level. If a cardholder has multiple cards assigned, they only need to have their biometric template enrolled once. The biometric reader will output as the card number once a valid finger is presented.

Association

When enrolling, the card number is used to associate records in the ZKBioPack software to the card within Access It! Universal.NET. Because the facility code is not used, duplicate card numbers are not allowed. When making modifications to the cardholder or to the card itself, those changes are associated by the respective CardholderID and CardID fields. This allows for changing the card number of an existing card and not needing to re-enroll a biometric template.

Synchronization

Upon initial installation of the ZKBioPack integration software, an initial synchronization is performed to populate all cards from Access It! Universal.NET into the ZKAccess database. Records existing in the ZKAccess database are not erased.

Each time the ZKBioPack  application is started, synchronization occurs between the databases. Records existing in the ZKAccess database are not erased.

Invixium (via IXM WEB)

Supported Models

All Invixium readers except the MERGE CR are supported. Minimum Firmware must be 1.5.0.0

Enrollment

Enrollment is performed at the card level. If a cardholder has multiple cards assigned, they only need to have their biometric template enrolled once. Within the IXM WEB software, only one of their cards can be marked as the "Biometric Card" which the reader will output as the card number once a valid finger is presented.

Association

When enrolling, the card number is used to associate records in the IXM WEB software to the card within Access It! Universal.NET. When making modifications to the cardholder or to the card itself, those changes are associated by the respective CardholderID and CardID fields. This allows for changing the card number of an existing card and not needing to re-enroll a biometric template.

Synchronization

Upon initial installation of the IXM WEB integration software, the database synchronization is configured. This process allows for configuring how often records are synced on a schedule.

Morpho 4G

Supported Models

4G V-Flex Lite (S,P) min f/w v4.4.6.0.3.a1.0

4G V-Flex (S) min f/w 4.1.11.0.2.a2.0

4G V-Station min f/w 4.1.11.0.2.a2.0

Enrollment

Enrollment is performed at the Cardholder level. If a cardholder has multiple cards assigned, they only need to have their biometric template enrolled once.

Association

Due to the integration being reliant on Mercury-Security, the association between the biometric record and the card is handled by the SCP controller and transparent within the software. Upon a card presentation, the SCP controller confirms if the reader requires biometric verification, loads up the cardholders template, and prompts the biometric reader to begin looking for a card. If the template matches then access is granted.

Synchronization

Biometric templates are saved in the SCP controller each time the cardholder or card is saved within Access It! Universal.NET.

More Information

Because this integration requires a card to be swiped prior to presenting a fingerprint, it is not possible to achieve a finger-only solution. Specific information on configuring these readers within Access It! Universal.NET can be found in:

4G V-Flex Lite (S,P)

4G V-Flex (S)

4G V-Station 


  • 501
  • 14-Mar-2018
  • 2298 Views