...
Release notes | 10.45  |
Table of contents
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Guide lines for 2500 card users and 250 readers and 5 concurrent users*.
Version | CPU | Ram | Disk |
10.45 | >= 2.0 Ghz dual core | 16 GB | >= 500GB |
Test system (small) | 1.6 Ghz dual core | 4 GB | 100GB |
...
The required operating system version for iProtect:
Version | O.S./ Firmware | Maintenance / serverboxiProtect version | Ubuntu lts | iProtect-setup | Servbox | Internet connection required |
iProtect 10.5 | Ubuntu 24.04 LTS | = > = 10.02.04xx3.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. |
...
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:
iProtect version | LinuxUbuntu lts | rootFS | |
|---|---|---|---|
10.1 or lower | Ubuntu 16.04 | V5-68a | |
10.2 - 10.4 | Ubuntu 20.04 | ≥ V6 | -12 .11.14 - V7-xx |
10.5 | or higherUbuntu 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.12 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
...
Hardware / Device | Software / Firmware (minimum) |
Pluto (RootFS) | 76.12.x03 |
Reader manager | 6.x ** |
Orion | 1.5.34 |
iX-serie Reader firmware | 32.x9x |
RIO firmware | 1.2.50 / 2.16.0 |
TANLock | 1.1.0.1.update.1151.100.00-0 |
| Note |
|---|
** IPROTECT Access version 10.5.01 includes Reader Manager, version 6. This version is required when using DOM OSS or SimonsVoss VCN. |
| 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
| 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
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.
General improvements are:
...
64bit database.
...
Log functionality by all services (for analyzing purposes).
...
Sense maintenance: Reduce the amount of getdivalist calls.
...
New date time format support carddata interpretation (DDxMMxYYYY where x could be any seperator).
...
4. iProtect server and application
In every new version of iProtect, there will be product improvements (bug fixes). The section below lists changes or newly added fucntionality compared to iProtect 10.4.
| Info |
|---|
IPROTECT Access version 10.5 is similar as a basis to the last released version 10.4. |
4.1 Free unique text field
In iProtect version 10.5 it is possible to use a unique free (pager) number (range). If the number already exists, you will get an error message.
button (next free number)
manual entry