...
Release notes | 10.4  |
Table of contents
| Table of Contents | ||||
|---|---|---|---|---|
|
1. Introduction
These release notes provide information about the latest features of iProtect, including required software versions and hardware installation and operating manuals.
2. System requirements
This chapter lists the required hardware and software for iProtect, including the licensing scheme of iProtect upgrades and other important information.
2.1 Supported servers
For installation and support of the iProtect server, the system requirements of Ubuntu server are followed. This may differ depending on system use and size.
In addition, the duration of support is determined by the lifespan of the hardware. This is issued by the hardware manufacturer and described as MTBF (Mean Time Between Failure).
2.2 Hardware specification
The hardware specification depends on many variables, so the required specification is customer specific.
...
| Info |
|---|
Deploying iProtect on a virtual environment, the performance of the disk read/write can be depended to the other virtual machine deployed on the same hypervisor. |
2.3 Software
The required operating system version for iProtect:
...
| Info |
|---|
On request there is an option to install iProtect without an internet connection but is not recommended. |
2.4 Update policy
TKH security works non-stop to improve its products and their safety.
From iProtect version 10.5, the software version from which you update and the software version to which you update must be taken into account.
Why is this change? The security policy prevents newly installed software from working or communicating with software that does not meet these security requirements, so that a roll-back will no longer work.
2.4.1 Which iProtect version supports which Pluto RootFS
To ensure a reliable and secure system, the following software versions are required:
...
| Info |
|---|
Before updating to iProtect version 10.5, controllers should be running RootFS v6.12 or higher. |
2.5 Software and firmware
Software versions of the connected hardware are managed from iProtect by default.
Below you will find an overview of the most used hardware and the minimum version that are installed (provisioned) when updating iProtect.
...
| 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. |
...
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:
...
| Info |
|---|
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 upgrading. |
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.
From version | To version | New license needed |
|---|---|---|
10.3.x | 10.4.x | Yes |
10.4.x | 10.5.x | Yes |
10.5.x | 10.5.x | No |
2.7 Browser support
All tests are done with default browser settings, if some functionalities require changes to the settings, this will be mentioned in the specific manual. The following browsers are supported in iProtect:
...
| Info |
|---|
Microsoft internet explorer (IE) is not supported anymore. |
3. End of support
Sirius 1 support in combination with Reader manager version 6
SimonsVoss SI2
Traka 32 support
3.1 Advance notice
Making use of the hta-tool can entail security risks. That was the reason we wanted to deprecate this.
Since many customers are still using this tool, an option has been added to continue using this hta tool. This usage is disabled by default.
...
Installation | Settings | System parameters, tab: Other, “HTA enable”.
3.2 Pre-announcement
3.2.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.2.2 Support of INVR / License plate recognition on Polyx and IPU-8
iProtect 10.4 will be the last version which supports an iNVR Node on a iPU-8 or Polyx controller. If this situation occurs, the advise is to move the INVR node to a local server line.
4. iProtect server and application
This chapter describes the additions and/or changes of the application.
...