...
Installation Manual | TM- |
20221227 iProtect Access / Security | Functionalities |  |
|
|
This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.
...
20face provides a contactless solution for office buildings using GDPR-proof facial recognition. The entire daily use (person management) is done by iProtect.
This document provides an overview of the functionalities and also the steps required to connect 20face and iProtect.
...
Below is an overview of support for both the hardware and the software, including the necessary license:
Support | Version | Maximum | License number |
|---|---|---|---|
iProtect | >= 10.1.xx |
IPS- |
ON online card reader license | |||
External services | |||
Pluto | |||
20face IDbox | Max. 4 per Pluto | ||
Virtual card readers | Max. 8 per Pluto |
| Info |
|---|
When using 20face, the 'calamity card' function cannot be used. |
...
The connection between the Pluto and the 20face IDbox is based on the OSDP protocol via TCP/IP. The IDbox is created within iprotect iProtect as Node. Several card readers can be linked to the 20face node, where the card reader is the camera that sends an ID when it recognizes a face.
...
The integration between iProtect and the 20face system offers the following functionalities:
Description | Details |
|---|---|
Full integration with 20face cloud solution |
|
Management, completely by iProtect |
|
Advanced functions available like |
|
5. Setup
20face is a cloud-based solution, which means that an internet connection is necessary. Before proceeding with the following chapters, check if iprotect iProtect can connect to the internet.
...
| Info |
|---|
Only the used fields are described in the table below. |
Field | Content | |
|---|---|---|
Name | Logical name e.g. 20face | |
Features | Node | OSDP |
OSP | ||
compatibility | Fully compliant | |
General | Name | Logical name is mandatory |
Login 20face | Username | Fill in username |
Password | Fill in Password | |
SSL | Use SSL | Default on |
Aloow self signed | Default on | |
Allow expired | Default on | |
No Hostname check | Default on | |
Client communication type | Less secure client communication | |
Status | Node online | Selection option to activate |
Address | HTTP port | 8888 |
IP address | IP address 20face IDbox | |
URL | Reserved future use (default “/”) |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
When using iProtect <=10.2 SSL settings are in de Node dialog. These settings can be determined depending on the situation. |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
When using iProtect > 10.2 SSL settings are moved to: Installation | Hardware | Secure communication type. These settings can be determined depending on the situation. |
...
In iProtect, browse to menu: Access | Settings | Card coding | Card number presentation.
Right click in the search field and choose “add Card number presentation”:
Field | Content |
Name | Logical name, e.g 20face |
Format | Personid as cardnumber |
5.2.2 Card data interpretation
...
In iProtect, browse to menu: Access | Settings | Card coding | Card data interpretation.
Right click on the “Card number presentation” that was just created and choose “add Card data interpretation”.
Field | Content | |
Name | Logical name, e.g 20face | |
Default card data interpretation | cardnumber is personid (press set) | |
Format | Reader communication protocol | ABA |
Card type | Decimal to data lenght | |
5.3 Configure the Service / database link
...
Right click in the search field and choose “add database link”
Select typ: 20face Face Recognition
Field | Content | Description | |
Name | Logical name. e.g 20face service | ||
Status | Active | “Checked” | |
Remote server | Login name | Enter the login name | Supplied by installer |
Password | Enter the password | Supplied by installer | |
Time out (sec.) | 45 | ||
Parameters | Project id | ||
Default 45 seconds, do not change unless adviced by TKH
Supplied by installer | |||
Card data interpretation | Select the 20face card data interpretation | ||
Main Domain | The Connection URL | ||
Authorization | Read | Everything |
6. Quick setup
6.1 Add person
...
The invitation has send (default valid for 7 days before it expires and a new invitation ha to be send). It can take a couple of minutes before the email arivesarrives. Please follow the instruction in the email to finalize the registration of the face recognition.
...
Search for the created card (See 56.3)
Select the card in treeview and open in the treeview the “card group list” and enable the card group(s).
7. Events
Type | Description |
|---|---|
System offline | If the network connection is lost between the Pluto and the IDbox, face recognition shall not be functional |
Date / Time | If an event has a * before the date/time stamp, it means that the correct time of the event does not have the expected timestamp. For example, this can be dated 1 Jan. 1970. iProtect will change the time to the current time marked with *. not to lose these events |
User logs in/out events | User log- in and out are the internal connection messages of iProtect with the service that is connected:
|
Webservice | Web server messages are messages about communication with the 20face cloud application:
|
Node events | Node events are messages about the connection between IDbox and Pluto:
|