...
iProtect version | Ubuntu lts | iProtect-setup | Servbox | Internet connection required |
10.5 | = > 3.1.0 | = >10.03.01 | Yes, for installation and updates |
...
| Note |
|---|
It is highly recommended to ensure that iProtect is connected to the internet during installation. Permanent access to the internet is of course possible, but temporary internet access for updating the security packages is also possible. |
| Info |
|---|
On request there is an option to install iProtect without an internet connection but is not recommended. |
...
iProtect version | Ubuntu lts | rootFS |
|---|---|---|
10.1 | 16.04 | V5-68a |
10.2 - 10.4 | 20.04 | V6.11.14 - V7-xx |
10.5 | 24.04 | V6.11.14 - v7-xx |
10.6 (future) | 24.04 | V7-xx |
| Info |
|---|
Although RootFS v5-68a is still supported by iProtect 10.2 and 10.3, this will no longer be the case when iProtect 10.4 or higher is used. |
| Info |
|---|
Before Run at least version 10.3 before updating to iProtect version 10.5, the system should first be updated to version 10.3 or higher with rootFS version 6.x. |
| Info |
|---|
Before updating to iProtect version 10.5, controllers should be running RootFS v6.11.14 or higher. |
| Note |
|---|
Before moving to IPROTECT Access 10.6 in the near future, the controllers should be equipped with rootFS v7.xx |
| Info |
|---|
When using rootFS version 6, OpenSSL1.x is used. When using rootFS version 7, OpenSSL3.x is used. |
2.5 Software and firmware
...
| Note |
|---|
** IPROTECT Access version 10.5.01 includes Reader Manager, version 6. This version is required when using DOM OSS or SimonsVoss VCN. |
** DOM OSS and SimonsVoss VCN did not work correctly with Reader Manager version 5.03 |
| Info |
|---|
Release notes of the software/firmware are available on request. |
| Info |
|---|
If software/firmware versions have a lower number than shown in the table above, it will be automatically updated. Although this time is kept as short as possible, the customer may be inconvenienced for a short time. |
| Info |
|---|
| Info |
When updating iProtect, all network controllers will be updated automatically to the latest RootFS version. This update will be processed in the background and will take approximately 10 - minutes (depending on network speed). During the preparation of the update, the customer will not experience any inconvenience. When the update is complete, the system administrator must reboot the controller. Booting up the controller will take approximately 2 minutes (depending on network speed). During this time, the customer may experience problems opening the door. |
2.6 Encrypted JDBC connection
| Info |
|---|
iProtect 10.5 requires an encrypted (SSL mode) jdbc connection. |
Required .Jar files for iProtect v10.03.xx and higher:
java-library-xx.x.x.jar
keyprocessor-jdbc-xx.x.x.jar
log4j-api-x.x.xx.jar
log4j-core-x.x.xx.jar
icu4j-73.1.jar
tyrus-standalone-client-x.xx.jar
2.6.1 API documentation available (on request)
If desired, new API documentation is available:
JDBC over SSL
iProtect XML API v2.16
| Info |
|---|
Please contact TKH-Security for these API documents. |
TKH security tries to keep the links working at all times, but cannot guarantee this in case of an upgrade. When connecting third-party systems to Protect, it is strongly recommended to test for proper operation with a preset test system before upgradingThe time of restart the controller, can be determined by the system administrator. It is recommended to perform this within 1 week time. |
2.6 License
When a major version number changes, it should be taken into account in advance that a new license is necessary. Please contact TKH Security service department or your account manager for this.
...
| Info |
|---|
Microsoft internet explorer (IE) is not supported anymore. |
2.8 API-support
Customers using the API are advised to test the link in an acceptance environment before the update is released in your environment.
| Info |
|---|
We do everything that we can to avoid making changes to the API. However, in some cases this is not possible (as an example security requirements and changes). We cannot be held responsible for changes to the API. |
3. End of support
Sirius 1 support in combination with Reader manager version 6
SimonsVoss SI2
Traka 32 support
Support of INVR / License plate recognition on Polyx and IPU-8
3.1 Pre-announcement
3.1.1 Network controller
Polyx Network controller: End of life: 31-12-2025
Apollo 1: End of life: 31-12-2025
iPU-8: End of life per: 31-12-2025
3.1.2 Support of INVR / License plate recognition on Polyx and IPU-8
...
| Info |
|---|
Removed from IPROTECT Access (Q3-Q4 2025) |
| Info |
|---|
The obsolete hardware will still be kept in an established version (iProtect LTS version). A contract for this will need to be concluded. More information on this will be available from your account manager later this year. |
3.2 Revised advance notice
...