...
| Informace | ||
|---|---|---|
| ||
If you are running 2N® Access Commander version 1.9.1 or older, proceed please to this section for further details. |
2N® Access Commander version 3.
...
3 (January 2025)
2N® Access Commander version 3.1 introduces a more secure method of login (2FA), Dutch Language and other improvement
**IMPORTANT** Due to security reasons this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running FW 2.37 or older. Access Commander will not manage devices with these FW even with enabled compatibility mode. Please ensure that all devices are running FW 2.38 or newer before upgrading.
New Features:
- Two Factor Authentication
Two factor authentication is now available for login. When enabled each user requires both password and secondary authentication via an authenticator app such as Google Authenticator in addition to their unique user name. This extra level of security can be optional for all users, mandatory for users with a role (Managers), or mandatory all users and is set by Admin. 2FA works even for installations that are offline (have no internet connection).
- Dutch Language
Dutch is now included as a language variant in Access Commander's web environment. The online and offline manual also supports machine translated Dutch.
- Other Improvements
* Access Commander now supports API Keys - access without user authentication opening up further possibilies for integration.
* When setting up Access Commander from the browser for the first time the linux root password is now synchronised with the system admin password if the root password hasn't yet been changed from default.
* Access Unit QR is supported in this version.
Corrections
* Device sensor (door sensor) status is now correctly displayed in the device monitoring page.
* User name for access granted/denied now displayed in the Access Log widget.
* Device configuration can now be accessed from the device list as it was in Access Commander version 2.
Additional notes
**IMPORTANT** - In May 2023 we announced that the old APIv2 will be retired in place of a more advanced APIv3 and gave a transition period of one year where the two versions run side by side. From this release APIv2 will be no longer supported, and will be removed completely from Access Commander 3.2 (Q3 2024).
If you are using Access Commander with a third-party integration, please ensure that this integration is compatible with APIv3 soon to avoid loss of functionality in future versions.
For more information on Access Commander's API see the documentation in the user manual
- The old user interface is no longer available in this version
- Known issue - In 3.1 it is not possible to manually approve a device firmware on a Basic (free) license. Please ensure all devices meet the firmware requirements listed below. Fix comming in Access Commander 3.2 (August)
- Integration with the Milestone Xprotect plugin is not compatible with 2FA. Do not enable 2FA for the Milestone user login.
Required device firmware versions for full feature support
2N IP intercoms 2.43.x
2N Access Unit 2.43.x
Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)
2N IP intercoms 2.39.x
2N Access Unit 2.393 introduces better support for devices in remote network segments, support for additional SIP accounts in our intercom products (FW 2.46 required) and enhances security by validating the unique device certificate of our connected devices.
This release includes security fixes and addresses concerns regarding two user reported vulnerabilities that will be published as CVEs. Security advisory to be published on 2n.com. It is strongly recommended that all users upgrade to version 3.3 to ensure the security of their installation.
New Features & Improvements:
Maintaining connection with remote devices
The current method of device discovery and then using that discovered IP address for connection works well for flat networks where our discovery protocol works unhindered, but when devices are on remote connections (eg, VPN, NAT or multi-segment topology) and the device IP address changes (such as a DHCP lease expiration) then the connection to this device is lost and cannot be reconnected. This release supports an optional mode where devices can report back to Access Commander via HTTP in the event of an address change.
Support for additional SIP accounts
Intercom firmware 2.46 now supports two additional SIP accounts (SIP 3 and 4) and a dedicated account for calling MS Teams extensions. Users in Access Commander can now be assigned phone numbers that call out via these accounts by applying the suffix /3, /4 or prefix ‘msteams:’ as appropriate.
For example, number ‘3008/3’ would call extension 3008 from an intercom’s third SIP account or ‘msteams:15684999’ would call number 15684999 via MS Teams. The status of these additional accounts can be monitored on the devices monitoring page and on the device detail page.
Device certificate fingerprint validation
Three security options are now available for connected devices.
- None - Communication will be encrypted (HTTPS), but certificates will not be validated. This mode is the default.
- Certificate Fingerprint Validation - Checks the certificate fingerprint of the device and verifies its match with approved values. This method provides good security for encrypted communication. Note - devices with mismatched or unrecognised certificate fingerprints will no longer be synchronised.
- Full Certificate Validation (PKI) - Performs a complete certificate check according to PKI rules and requires certificates from trusted authorities. This option provides the highest level of security for encrypted communication. Devices without valid certificates signed by a trusted authority will no longer be synchronised.
Support for RFID card compatibility mode
RFID card compatibility mode allows cards with trailing characters that match, regardless of their overall length, to be treated as identical. Enabling this feature applies compatibility mode across all connected intercoms and access units. Prior to the introduction of this option, cards that 2NOS would recognize as identical were inconsistently handled by Access Commander, resulting in some cards being rejected when assigned to a user.
Additional Notes
IMPORTANT - In May 2023, we announced the retirement of APIv2 in favour of our more advanced APIv3, with a one-year transition period where both versions were supported. Since version 3.2, APIv2 has been completely removed from Access Commander, and any integrations relying on APIv2 will no longer function. For more information on Access Commander’s API, please refer to the documentation in the user manual.
IMPORTANT - For security reasons, this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running firmware version 2.37 or older. Access Commander will not manage devices with these firmware versions even if compatibility mode is enabled. Please ensure all devices are running firmware version 2.38 or newer before upgrading.
Required Device Firmware Versions for Full Feature Support
- 2N IP Intercoms: 2.46.x
- 2N Access Unit: 2.46.x
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
- 2N IP Intercoms: 2.42.x
- 2N Access Unit: 2.42.x
- 2N Indoor Touch 2.0: 4.3.x (
...
- Devices running earlier versions
...
- will be disabled in Access Commander)
- 2N Indoor Touch 1.0 is not supported in Access Commander
API
...
Changes
- [APIv3 Change
...
- Log] https://www.2n.com/
...
-----
2N® Access Commander version 3.0 (production February 2024)
2N® Access Commander version 3.0 introduces a brand new look and feel. While the look has changed, it's the same trusted Access Commander, now more user-friendly, simplified and intuitive.
Changelog 3.0
New interface
New improvements
Mobile friendly visitor enrolment
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2N® Access Commander version 3.2.2 Firmware Support & Bugfix (Production December 2024)
This release adds support for 2NOS FW 2.46 (released in December 2024).
2N® Access Commander version 3.2 introduces automation capabilities, the ability to assign logical names to installations, and several other security and usability enhancements. Please note that APIv2 has been removed in this version. Ensure that any third-party applications previously utilising APIv2 have been updated to version 3, specifically 2N Picard Commander and 2N Milestone plugin. Please go to the 2N website and download new versions of these applications.
This release includes security fixes and addresses concerns regarding the following user reported vulnerabilities.
- CVE-2024-47253, CVSS 7.2 Path Traversal vulnerability could allow an attacker to write files on the filesystem to achieve arbitrary remote code execution.
- CVE-2024-47254, CVSS 6.3 Insufficient Verification of Data Authenticity vulnerability could allow an attacker to escalate their privileges and gain root access to the system.
- CVE-2024-47255, CVSS 4.7 Local attacker can escalate their privileges in the system which could allow for arbitrary code execution with root permissions.
It is strongly recommended that all users upgrade to version 3.2 to ensure the security of their installation.
New Features:
Automation (Node-RED)
Node-RED has been integrated into Access Commander. Node-RED, a flow-based programming tool from the OpenJS Foundation, allows users to create custom automations by connecting ‘nodes.’ These automations can facilitate simple or complex integrations with third-party APIs or trigger custom scenarios within Access Commander itself. The Access Commander implementation of Node-RED includes six custom nodes that enable automations based on System and Access Log events, SignalR topics, REST API queries, and a dedicated node for writing events to the system log. Automation is available only to users with Admin-level login rights.
- IMPORTANT - Please read bottom of release notes for more information about Automation and our disclaimer.
Installation Naming
You can now assign a name to each Access Commander installation through Settings > Configuration. This name will be displayed in the application header, browser tab, and all outgoing e-mail notifications. This feature is particularly useful for administrators or installers managing multiple instances of Access Commander, making it easy to identify the origin of each e-mail.
Other Improvements
- FTP and LDAP TLS server certificates can now be validated against trusted certification authorities, reducing the risk of ‘man-in-the-middle’ attacks.
- User Managers can now view card IDs in user logs (previously restricted to Admin users only). This feature is useful for copying card IDs during the onboarding of new users. The setting is disabled by default but can be enabled in Settings > Credentials.
- Support for encrypted (password-protected) device backups in alignment with 2NOS.
- The SIP proxy state of intercoms on the device detail and monitoring pages now accurately reflects the true status of each account (SIP Disabled, Registering, Registered, etc.).
- The 2N Mobile Key application has been integrated into the My2N app. All references to 2N Mobile Key have been removed from this release, and the Bluetooth pairing e-mail now directs new users to download the My2N app.
Corrections
- Installations using the Basic license can now manually approve ‘incompatible’ device firmware versions.
- Door Managers can now hold doors open directly from the door widget.
- Presence can now be enabled without requiring an attendance license.
Additional Notes
IMPORTANT - In May 2023, we announced the retirement of APIv2 in favor of the more advanced APIv3, with a one-year transition period where both versions were supported. As of this release, APIv2 has been completely removed from Access Commander, and any integrations relying on APIv2 will no longer function. For more information on Access Commander’s API, please refer to the documentation in the user manual.
IMPORTANT - For security reasons, this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running firmware version 2.37 or older. Access Commander will not manage devices with these firmware versions even if compatibility mode is enabled. Please ensure all devices are running firmware version 2.38 or newer before upgrading.
Integration with the Milestone XProtect plugin is not compatible with 2FA. Do not enable 2FA for the Milestone user login.
Required Device Firmware Versions for Full Feature Support
- 2N IP Intercoms: 2.46.x
- 2N Access Unit: 2.46.x
Minimum Supported Firmware Versions (Devices running firmware older than these versions will not sync with Access Commander)
- 2N IP Intercoms: 2.40.x
- 2N Access Unit: 2.40.x
- 2N Indoor Touch 2.0: 4.3.x (Devices running earlier versions will be disabled in Access Commander)
- 2N Indoor Touch 1.0 is not supported in Access Commander
API Changes
- [APIv3 Change Log] https://www.2n.com/documents/22902/2323545/Diffv3_v3.1-v3.2/fc475e95-62dd-46ed-810b-293e24e63d33
Automation in 2N Access Commander
We are pleased to announce the introduction of a powerful new Automation feature in 2N Access Commander, available under the Advanced, Pro, and Unlimited licences. Built upon the robust Node-RED platform, this addition brings extensive flow-based programming capabilities directly to our software, allowing users to seamlessly connect 2N Access Commander with various third-party systems and automate custom workflows based on events within the platform.
If you wish to take advantage of this versatile automation tool, please bear in mind the following:
Customer Responsibility for Security:
Users are responsible for ensuring that their Automation configurations and workflows are secure and in line with cybersecurity best practices. This includes securing the Node-RED environment, managing permissions appropriately, and safeguarding sensitive data within your automations.
Use of the REST API node:
If not used properly this node may lead to data loss or unintended modifications. It is the user’s responsibility to ensure that the node is configured and implemented correctly. Please exercise caution and double-check your settings to avoid potential risks to your data.
Third-Party Nodes and Add-ons:
2N is not responsible for the use or integration of any third-party nodes, add-ons, or custom modifications to Node-RED within the Automation feature. Customers should carefully evaluate and ensure the security and stability of any additional components they choose to install. Any issues arising from third-party extensions will need to be resolved by the customer or the respective third-party provider.
Technical Support Limitations:
While our support team will assist with issues related to the basic functionality of the Automation feature within 2N Access Commander, including our custom Access Commander nodes, they will not be able to provide assistance with the design, development, or debugging of custom Node-RED flows. Users who wish to create complex automations may need to seek additional support from qualified Node-RED experts or consult available resources.
For those looking to get started with Node-RED, we recommend exploring the wealth of online resources available, such as detailed manuals and numerous YouTube tutorials, which provide guidance on creating and managing your own flows.
For more information about our custom 2N Access Commander nodes and using the Automation feature within 2N Access Commander, please refer to our manual.
We believe this new feature will significantly enhance the capabilities of 2N Access Commander, and we encourage you to explore its potential, keeping in mind the importance of securing your configurations.
Thank you for your understanding.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2N® Access Commander version 3.1.1 (Production June 2024)
2N® Access Commander version 3.1.1 includes support for Intercom and Access Unit firmware 2.44 and a few minor bug fixes in addition to the features introduced by 3.1 listed below.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2N® Access Commander version 3.1 (production April 2024)
2N® Access Commander version 3.1 introduces a more secure method of login (2FA), Dutch Language and other improvement
**IMPORTANT** Due to security reasons this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running FW 2.37 or older. Access Commander will not manage devices with these FW even with enabled compatibility mode. Please ensure that all devices are running FW 2.38 or newer before upgrading.
New Features:
- Two Factor Authentication
Two factor authentication is now available for login. When enabled each user requires both password and secondary authentication via an authenticator app such as Google Authenticator in addition to their unique user name. This extra level of security can be optional for all users, mandatory for users with a role (Managers), or mandatory all users and is set by Admin. 2FA works even for installations that are offline (have no internet connection).
- Dutch Language
Dutch is now included as a language variant in Access Commander's web environment. The online and offline manual also supports machine translated Dutch.
- Other Improvements
* Access Commander now supports API Keys - access without user authentication opening up further possibilies for integration.
* When setting up Access Commander from the browser for the first time the linux root password is now synchronised with the system admin password if the root password hasn't yet been changed from default.
* Access Unit QR is supported in this version.
Corrections
* Device sensor (door sensor) status is now correctly displayed in the device monitoring page.
* User name for access granted/denied now displayed in the Access Log widget.
* Device configuration can now be accessed from the device list as it was in Access Commander version 2.
Additional notes
**IMPORTANT** - In May 2023 we announced that the old APIv2 will be retired in place of a more advanced APIv3 and gave a transition period of one year where the two versions run side by side. From this release APIv2 will be no longer supported, and will be removed completely from Access Commander 3.2 (Q3 2024).
If you are using Access Commander with a third-party integration, please ensure that this integration is compatible with APIv3 soon to avoid loss of functionality in future versions.
For more information on Access Commander's API see the documentation in the user manual
- The old user interface is no longer available in this version
- Known issue - In 3.1 it is not possible to manually approve a device firmware on a Basic (free) license. Please ensure all devices meet the firmware requirements listed below. Fix comming in Access Commander 3.2 (August)
- Integration with the Milestone Xprotect plugin is not compatible with 2FA. Do not enable 2FA for the Milestone user login.
Required device firmware versions for full feature support
2N IP intercoms 2.43.x
2N Access Unit 2.43.x
Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)
2N IP intercoms 2.39.x
2N Access Unit 2.39.x
2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)
2N Indoor Touch 1.0 is not supported in Access Commander
API changes
* [APIv2 Change log] No changes were made
* [APIv3 Change log] https://www.2n.com/documents/22902/2323545/Diffv3_v3.0-v3.1+2.md/c8a5ad20-6179-4902-b8a5-81a8f26d50d1
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2N® Access Commander version 3.0.1 BugFix (Production April 2024)
IMPORTANT Due to security reasons this version of Access Commander is not compatible with 2N Intercoms and 2N Access Units running FW 2.37 or older. Access Commander will not manage devices with these FW even with enabled compatibility mode. Please ensure that all devices are running FW 2.38 or newer before upgrading.
Supported device firmware version:
2N IP Intercoms from 2.38.x to 2.43.x
2N Access Units from 2.38.x to 2.43.x
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2N® Access Commander version 3.0 (production February 2024)
2N® Access Commander version 3.0 introduces a brand new look and feel. While the look has changed, it's the same trusted Access Commander, now more user-friendly, simplified and intuitive.
Changelog 3.0
New interface
New improvements
Mobile friendly visitor enrolment
Russian language support has been removed from Access Commander 3.0
Access Commander 3.0 includes the ability to toggle back to the old interface. It's worth noting that starting from version 3.1, only the new interface will be available, and the old interface will no longer be supported.
Upgrade to PostgreSQL 15
Supported device firmware version:
* 2N IP intercoms from 2.38.x to 2.42.x
* 2N Access Unit from 2.38.x to 2.42.x
* 2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)
**IMPORTANT**
In May 2023 we announced that the old APIv2 will be retired in place of a more advanced APIv3 and gave a transition period of one year where the two versions run side by side. From Access Commander 3.1 (Q2 2024) APIv2 will be no longer supported, and will be removed completely from Access Commander 3.2 (Q3 2024).
If you are using Access Commander with a third-party integration, please ensure that this integration is compatible with APIv3 soon to avoid loss of functionality in future versions.
For more information on Access Commander's API see the documentation in the online manual
* Russian language support has been removed from Access Commander 3.0
Access Commander 3.0 includes the ability to toggle back to the old interface. It's worth noting that starting from version 3.1, only the new interface will be available, and the old interface will no longer be supported.
Upgrade to PostgreSQL 15
Supported device firmware version:
* 2N IP intercoms from 2.38.x to 2.42.x
* 2N Access Unit from 2.38.x to 2.42.x
* 2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)
**IMPORTANT**
In May 2023 we announced that the old APIv2 will be retired in place of a more advanced APIv3 and gave a transition period of one year where the two versions run side by side. From Access Commander 3.1 (Q2 2024) APIv2 will be no longer supported, and will be removed completely from Access Commander 3.2 (Q3 2024).
If you are using Access Commander with a third-party integration, please ensure that this integration is compatible with APIv3 soon to avoid loss of functionality in future versions.
For more information on Access Commander's API see the documentation in the online manual
* Russian language support has been removed from Access Commander 3.0
API changes
* [APIv2 Change log](https://www.2n.com/documents/22902/74426/APIv2+change+log+-+2N%C2%AE+Access+Commander+3.0.md/94202e31-ba91-4b16-9679-a4474581b2a9)
* [APIv3 Change log](https://www.2n.com/documents/22902/74426/APIv3+change+log+-+2N%C2%AE+Access+Commander+3.0.md/d3581281-c2e2-4115-a86a-c64d85d4210f)
API changes
* [APIv2 Change log](https://www.2n.com/documents/22902/74426/APIv2+change+log+-+2N%C2%AE+Access+Commander+3.0.md/94202e31-ba91-4b16-9679-a4474581b2a9)
* [APIv3 Change log](https://www.2n.com/documents/22902/74426/APIv3+change+log+-+2N%C2%AE+Access+Commander+3.0.md/d3581281-c2e2-4115-a86a-c64d85d4210f)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2N® Access Commander version 2.7.1 (production November 2023)
2N® Access Commander version 2.7.1 supports new version of firmware, that will be released.
Changelog 2.7.1
Supported device firmware version:
- 2N IP Intercoms from 2.36.x to 2.42.x
- 2N Access Unit from 2.36.x to 2.42.x
---
2N® Access Commander version 2.7 (beta August 2023, production August 2023)
2N® Access Commander version 2.7 introduces export of user list and possibility to assign credentials to users in bulk.
Changelog 2.7.0
New Features:
- User list export - Access Commander now allows exporting User list in a form of CSV file with various attributes (e.g. zones and doors that users can enter or groups to which they belong). It is also possible to export a sync file containing users data, edit it and then synchronize again so that the changes in CSV are propagated back to Access Commander. User list exports are especialy useful when the user data stored in Access Commander is supposed to be used by another system or when external auditor without access to Access Commander needs to check the data and possibly make necessary changes.
Assigning credentials to users in bulk - It is now possible to assign PIN codes, QR codes and Bluetooth pairing PIN codes to multiple users at once. This significantly reduces the time of new users onboarding. Email template for Bluetooth credentials can newly be edited in the same way as the other email templates so that admins may adapt its content to their company needs and make their users better perceive it. To increase security when a large number of pairing PIN codes is active, the number of PIN code digits has been increased from 6 to 8.
...
- 2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)
---
2N® Access Commander version 2.6.1 (June 2023)
...