Previous page Adding the Virdi fingerprints  ZK Teco Integration Module Settings Guide Next page


To configure Virdi user parameters in ACFA Intellect, do the following:

  1. In the Access Manager software module, open the user editing form (for details, see Editing a user).
  2. In the editing form that opens, select Virdi. Options (1) and then click the Not yet configured button (2).
  3. The User parameters (Virdi) form will open. In this form, select an object to be configured:
    1. Virdi Server;
    2. Virdi ACU;
    3. Virdi Terminal.
      Authorization of the Virdi Server object is enabled by default. To enable authorization of Virdi ACU and Virdi Terminal objects, set the Specify checkbox (1). After that, the parameters of these objects can be set.
  4. If the user should not be added to the device, set the Do not write to device checkbox (1). In this case, in Terminal mode, the user will be considered an unknown user, and access for this user will be denied (see Virdi Terminal operation settings).
  5. Set the Identify (1:N) checkbox (2) to enable the recognition option. Depending on the selected authentication type (7), user biometric data can be checked with the device database during the recognition. The check may take a long time depending on the amount of data in the database.
  6. Set the Face identification 1:N checkbox (3) so that the face is recognized first, and then this face is checked against the entire face database of the device. The check may take a long time depending on the number of faces in the database.
  7. Set the Administrator checkbox (4) to disable the settings on the device and allow only a user with the administrator role to change the settings.
  8. Set the Denylist checkbox (5) to enable the ability to add users to the blacklist.
  9. From the Security level drop-down list (6), select the required authentication quality level, from Lowest to Highest. The default value is Normal.
  10. From the Authentication drop-down list (7), select the authentication type:
    • Fingerprint is only a fingerprint.
    • Fingerprint in card (*) is a fingerprint attached to the card.
    • Password is a password only.
    • Card is only a card.
    • Card or Fingerprint is either a card or a fingerprint.
    • Card + Fingerprint is a combination of a card and a fingerprint.
    • Card or password is either a card or a password.
    • Card + password is a combination of a card and a password.
    • (ID or Card) + Fingerprint is a combination of a user ID or a card, and a fingerprint.
    • (ID or Card) + Password is a combination of a user ID or a card, and a password.
    • Fingerprint + Password is a combination of a fingerprint and a password.
    • Password, if Fingerprint failed is a password if fingerprint authentication failed.
    • Card + Password + Fingerprint is a combination of a card, a password, and a fingerprint.
    • Face is only a face.
    • Face or password is either a face or a password.
    • Card or face is either a card or a face.
    • Fingerprint or face is either a fingerprint or a face.
    • Card or fingerprint or face is either a card or a fingerprint or a face.
    • Card + face is a combination of a card and a face.
    • (ID or Card) + face is a combination of a user ID or a card, and a face.
    • Fingerprint + face is a combination of a fingerprint and a face.
    • Face + password is a combination of a fingerprint and a password.
    • Card + fingerprint + face is a combination of a card, a fingerprint, and a face.
    • Card + face + password is a combination of a card, a face, and a password.
    • Fingerprint + face + password is a combination of a fingerprint, a face, and a password.
    • Card + fingerprint + face + password is a combination of a card, a fingerprint, a face, and a password.
  11. To save the changes, click the OK button (8).

Note

If the Virdi user settings are configured in the Access Manager, they will take precedence over the settings of the Virdi terminal/Virdi server. If the settings in the Access Manager are not configured, then the decision depends on the Virdi terminal/Virdi server.

  • No labels