...
iProtect Roadmap
...
| Table of Contents |
|---|
1. Introduction
A detailed schedule will be issued for the current and upcoming release. Planning for a release runs approximately over a time frame of 3 months.
Once development has started, a new schedule is made with stakeholders for the next release.
2. Planning
2.1. IPROTECT: Release 10.4
| Roadmap Planner | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
DOM support in iProtect Mobile Access
2.1.1 Details release 10.4
...
Priority
...
Description
...
Type
...
Short description
...
Ticket
...
Time estimate
...
FAT date *
...
SAT date *
...
Project leader
...
Notes
...
DOM support in iProtect Mobile Access
...
strategic
...
Sales
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Minimize impact: iProtect update (Local database Pluto)
...
strategic
...
iProtect CLOUD
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
iProtect functionality: On/Off
...
strategic
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
3wk
...
DORMA KABA (OSS)
...
Support 802.1x on Server
...
Customer
...
PI
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
2wkn
...
?
...
SimonsVoss Maintenance
...
Maintenance
...
Ticket and issues will be reviewed. Not all tickets will be solved because of the time.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
3wk
...
1
...
Support of PIN code keypads ( Simons & Voss - Wireless online)
...
Customer
...
Windmill park TKH Germany
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
august 2023
...
Marcel van Kersbergen
...
Fairplay Certus / 20face
...
strategic
...
4wkn
...
Peter vd Brink
...
Meta data
...
strategic
...
Preparation for PostgreSQL
...
Factory Acceptance Testing (FAT) and Site Acceptance Testing (SAT) are collectively referred to as commissioning. It is part of the Good Engineering Practices.
...
Priority
...
Description
...
Type
...
Short description
...
Ticket
...
Time estimation
...
FAT date *
...
SAT date *
...
Project leader
...
Notes
...
Priority
...
Pluto: Support ACaaS (“VPN”)
...
?
...
?
2.1.1.1 Details: DOM support in iProtect Mobile Access
...
Short description
...
Estimated time line
...
Finished
...
Support DOM online cylinder and door handles through iProtect
...
Target date: 1-04-2022
...
...
Sent invitation to mobile through iProtect
...
...
Access when presenting a mobile device on an offline lock throught Cosmos Access
...
...
Access when presenting a mobile device on a Sirius iX through Cosmos Access
...
...
Multiple Node support
...
...
Password management
...
...
Backup Bridge
...
...
Linking a lock to a bridge
...
...
Linking a lock to a door
...
...
Support DOM RF/NM
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Configure RF NM in iProtect (Link readers)
...
...
Reader state (Automatic/Open/Closed)
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Pulse reader
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Fix existing OSS (Dorma Kaba, DOM OSS, Assa Abloy,)
...
...
Reorganize events
...
...
Scheduled tokens
...
In progress
...
...
Support DOM lock event upstream through Cosmos Access and iProtect
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Battery management (events / status)
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Multi site code support
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
...
2.2. iProtect release 10.5 (before 31-12-2023)
...
Priority
...
Description
...
Type
...
Short description
...
Ticket
...
Time estimation
...
FAT date *
...
SAT date *
...
Project leader
...
Notes
...
1
...
Single sign-on
...
Strategic
...
PI
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
1m + 2m
...
April 2023
...
December 2023
...
Needed: a functional description @Mark knops
...
1
...
Implementation - Support biometrics
...
Strategic
...
ICC / Eurojust
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
4wkn
...
Q1 2024
...
Which hardware/reader are we going to support? Prices?
...
1
...
Deister improvements
...
Customer
...
PI
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
2wkn
...
1
...
UTC time
...
Strategic
...
Preparation for PostgreSQL
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
4wkn
...
1
...
Integration of pagerservices
...
Customer
...
PI
...
?
...
June 2023
...
Q1 2024
...
Mark Knops
...
PI Zwolle: Minimaal de volgende gegevens dienen vanuit het toegangscontrolesysteem te worden opgehaald: naam; personeelsnummer; functie; afdeling
...
Support of Tatile Vega BASIC MK2 (STARK platform)
...
Customer
...
C&C partners
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Leszek Schmidt
...
ANSSI certificering
...
Strategic
...
France
Factory Acceptance Testing (
FAT) and Site Acceptance Testing (SAT) are collectively referred to as commissioning. It is part of the Good Engineering Practices.
4.1 Other parts, Not iProtect related
...
Priority
...
Description
...
Type
...
Short description
...
Ticket
...
Time estimation
...
FAT date *
...
SAT date *
...
Project leader
...
Notes
...
Priority
...
Reader manager: Empty biometric container PHG to re-use the card
...
CC
...
1wk
...
Needed: a functional description (@Sander Zonnveld)
...
Reader manager: Security update
...
SR
...
Secure communication with the reader
...
OSDP t=cl support
...
SR
3.1 iProtect release 10.6 (2024)
...
Priority
...
Description
...
Type
...
Short description
...
Ticket
...
Time estimation
...
FAT date *
...
SAT date *
...
Project leader
...
Notes
...
Priority
...
CUSTOMER
...
Customers would like an export regarding the access rights, but then seen from the reader/door.
...
Customer
...
NS
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Mark Sloot
...
CUSTOMER
...
Export (CSV) possibility: Hardware overview per line
...
Customer
...
NS
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Mark Sloot
...
User login of the TANlock should be changed after iProtect has started the communication with the TANlock
...
Maintenance
...
Security
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
TANlock will implement this end Sept. 2023
...
We should be able to use more card technologies with TANlock
...
Customer
...
Sales request
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
TANlock will implement this end Sept. 2023
...
Simplify the line dialog
...
Maintenance
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Update jasper reports (deprecation)
...
Maintenance
...
Security
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
No logout button in maintenance page
...
Maintenance
...
Security
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Img, video and canvas (deprecation)
...
Maintenance
...
Security
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Use a One Time Password (OTP) for the Java service
...
Maintenance
...
Security
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Hide Technical passwords
...
Maintenance
...
Security
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
CUSTOMER
...
Standardize Reporting / External event service
...
Customer
...
General
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
2wkn
...
Ziggo, NS
7. Long term roadmap
...
Ticket
...
iProtect to new environment (Postgres)
...
Ziggo, NS, Pro-rail, Politie, Hospital DE https://www.postgresql.org/
...
New controller line (Pluto / Orion)
...
DOM: Locker functionality
...
License structure
...
TrakaWeb, keyfob management
...
Card enrollment in iProtect
...
iProtect: Online (repository) update
...
Logical and Physical Acces?
| View file | ||
|---|---|---|
|
...
Support of Docker container (IPROTECT CLOUD)
...
TKH Germany, NS, https://www.oracle.com/nl/cloud/cloud-native/container-registry/what-is-docker/
...
New controller line : Cloud support
...
Generic TKH reporting mechanism
...
iX card reader OSDP t=cl support
...
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.
Guide lines for 2500 card users and 250 readers and 5 concurrent users*.
Version | CPU | Ram | Disk |
10.5 | >= 2.0 Ghz dual core | 16 GB | >= 500GB |
Test system (small) | 1.6 Ghz dual core | 4 GB | 100GB |
| Info |
|---|
For large systems (>1000 readers, >20 concurrent users), a minimum of 32GB internal memory and 8 cores is recommended. * |
| Info |
|---|
Depending of the use of images (keymaps, photo’s), the disk space should be checked. |
| 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:
iProtect version | Ubuntu lts | iProtect-setup | Servbox | Internet connection required |
10.5 | = > 3.1.0 | = >10.03.01 | Yes, for installation and updates |
For iProtect 10.05 and Ubuntu 24.04, there is a TKH repository with all needed files for installing and maintaining the setup files.
The operating system can be downloaded from Ubuntu's default repository.
| Note |
|---|
It is highly recommended to ensure that iProtect is connected to the internet during installation. |
| 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.
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 | 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 |
|---|
Run at least version 10.3 before updating to iProtect version 10.5. |
| 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
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.
Hardware / Device | Software / Firmware (minimum) |
Pluto (RootFS) | 6.12.03 |
Reader manager | 6.x ** |
Orion | 1.5.34 |
iX-serie Reader firmware | 2.9x |
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 |
|---|
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. The 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.
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:
Browser | Version |
|---|---|
Google Chrome | 132.0 |
Mozilla Firefox | 134.0 |
Microsoft Edge | 132.0 |
| 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.
The following option has been added to the dialog:
Installation | Settings | System parameters, tab: Other, “HTA enable”.
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