Previous page General information about two-factor verification  Face temperature monitoring and control Next page


Two-factor verification includes configuration on the ACFA side and on the Face side.

Configuring the two-factor verification on the ACFA side

To configure two-factor verification, do the following:

  1. On the Hardware tab of the System settings dialog box, create the Virtual access server object (1), based on the Computer object.
  2. Create the FACE verificator object (2), based on the Virtual access server object, and go to its settings panel.
  3. From the Camera drop-down list (1), select the camera that captures the faces. The camera should work as part of the Face Recognition Server (see Configuring the Face Recognition Server object).
  4. From the Server drop-down list (2), select the Face Recognition Server.
  5. From the Control drop-down list (3) select the access granting mode:
    • Server decides—depending on the result of the access rights check or face verification, the access is granted or denied.
    • Always redirect—regardless of the result of the second stage, the verifier redirects its solution to the external verifier (Event Manager/Photo ID/Script). Depending on the result, the access is granted or denied.
    • Redirect on failure—if the first stage is successful, then this mode is similar to the Server decides mode. If the first stage is failed, then the solution is delegated to the external verifier.
    • Redirect on success—if the first stage is failed, then this mode is similar to the Server decides mode. If the first stage is successful, then the solution is delegated to the external verifier.
  6. In the Timeout field (4), enter the time in seconds after which the connection with the Face Recognition Server is terminated.

  7. If necessary, in the fields of the Cache parameters group (5), set the parameters that are specific for each ACS integration module.

    Note

    For example, in the PERCo-S-20 v.2 integration module, each request to the operator is accompanied by the request_id parameter. This parameter should be returned when confirming access, otherwise the command will be ignored. For the Noder ACS, such parameter is param1.

  8. Set the Generate custom Access granted / Access denied event checkbox (6) if it is necessary that the FACE verificator object generates an additional event about granting/denying access, and specifies the reason for the denial. These events can be used to work with scripts or the Event manager interface module.
  9. From the Object type drop-down list (7), select the type of object that will initiate the face check. Typically, this is an access point, reader, etc.
  10. From the Object drop-down list (8), select the object of the type specified above.
  11. From the Event drop-down list (9), select the event by which the face check will be launched. The list of available events depends on the selected object type.

  12. From the Reaction for access drop-down list (10), select the command that will be sent to the initiating object upon the successful face verification. The list of available commands depends on the selected object type.

  13. From the Reaction for denial drop-down list (11), select the command that will be sent to the initiating object upon the unsuccessful check/face verification. The list of available commands depends on the selected object type.

  14. On the Rights tab (12), from the Mode drop-down list (13) select the access rights checking mode:
    • Recognition only—the server makes the access granting decision based only on face verification.
    • Rights checking—the server makes the access granting decision after successful verification of user access rights (access level, time zones, blocking, antipassback) and, then, successful face verification. If at the stage of checking access rights, a discrepancy in rights is found, then the device will be prompted to deny access, and face verification will not be started. The access denial event from the FACE verificator object will not be displayed in the Event viewer. If this mode is selected, the following settings become available:

      • Check date of begin and Check expiration—sets the mode of checking the access card validity:

        • Do not check—do not check the start or expiration date of the card.

        • Do not include—do not include the start or expiration date of the card in the check.

        • Include—include the start or expiration date of the card in the check.

      • Check blocking—set the checkbox to check if the user is blocked.
      • Check AntiPassBack—set the checkbox to control double pass.

  15. Go to the Mask tab (1) and set the Restrict access if checkboxes (2) to deny access in cases marked by the checkboxes. If none of the checkboxes is set in this block of settings, the mask recognition will be ignored.

  16. Go to the Temperature tab (1) and from the Mode drop-down list (2) select one of the options:

    1. Do not control—regardless of the temperature, the recognized person will be allowed access.
    2. Threshold exceeding—access denied if the temperature threshold set in the Face Recognition Server on the Analytics tab is exceeded (for details, see Face Recognition Server settings panel).
    3. Range—in the Lower threshold (1) and Upper threshold (2) fields, specify the minimum and maximum allowable temperatures, respectively. Access is allowed if the recognized person's temperature is within the specified range.

  17. Click the Apply button (14) to save the settings.

An example of the two-factor verification configured for the Noder ACS integration module is presented below.

The two-factor verification on the ACFA side is configured.

Configuring the two-factor verification on the Face side

Two-factor verification doesn't require the face database.

On the Face side, do the following:

  1. On the Hardware tab of the System settings dialog box, create the Face Recognition Server object, based on the Computer object.
  2. Based on the Face Recognition Server object, create the Recognition channel and Tevian recognition module objects.

The two-factor verification on the Face side is configured.

  • No labels