...

2N® Access Commander version 3.3

...

.1 Firmware Support & Bugfix (April 2025)

2N® Access Commander version 3.3 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

...

have been published as CVEs.

...

More details can be found on our website - www.2n.com/en-GB/newsroom/latest-cve-disclosures-reinforce-our-commitment-to-cybersecurity/. 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

...

Corrections:

• Fixed a bug which caused problems when changing the password of a connected device.
• Attendance export now includes timestamp when user doesn't clock out.
• Addressed an issue with LDAP login.
• Card ID is now included in access logs for all card access events.

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

  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.4647.x
• 2N Access Unit: 2.4647.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/-/media/Files/Web/downloads/diffv3_v3_2_v3_3

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

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.3 (January 2025)

2N® Access Commander version 3.3 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/-/media/Files/Web/downloads/diffv3_v3_2_v3_3

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 3.2.2 Firmware Support & Bugfix (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/en-US/download/diffv3_v31v323md

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 (production April 2024)

...

-------------------------------------------------

2N® Access Commander version 3.1.1 Firmware Support & Bugfix (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 (April 2024)

2N® Access Commander version 3.1 introduces a more secure method of login (2FA), Dutch Language and other improvement

...

* [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

...

Firmware Support & Bugfix (

...

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.

...

• 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

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 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

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 Firmware Support & Bugfix (

...

November 2023)

2N® Access Commander version 2.7.1 supports new version of firmware, that will be released.

...

• 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 (

...

August 2023

...

)

2N® Access Commander version 2.7 introduces export of user list and possibility to assign credentials to users in bulk.

...

• 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.

Corrections:

• Device monitoring upgrade issue fixed.

...

• 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)

Please note that this version is a minor release, further to the release of version 2.6 in May 2023. It introduces no new feature and only brings a specific bugfix. 

Changelog 2.6.1

Corrections:

• Fixed issue with backup creation/restore.

2N® Access Commander version 2.6 (beta May 2023, production May 2023)

2N® Access Commander version 2.6 introduces new API v3.

Changelog 2.6

New features:

...

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.6.1 Firmware Support & Bugfix (June 2023)

Please note that this version is a minor release, further to the release of version 2.6 in May 2023. It introduces no new feature and only brings a specific bugfix. 

Changelog 2.6.1

Corrections:

• Fixed issue with backup creation/restore.

2N® Access Commander version 2.6 (May 2023)

2N® Access Commander version 2.6 introduces new API v3.

Changelog 2.6

New features:

• API v3
• API received a major overhaul in version 3 (APIv3) for easier integration. Users, devices (and other entities) can now be created with all properties in a single POST request, where APIv2 needed separate requests to add every RFID card, phone number, etc. APIv3 also supports PATCH, so to change a single user property, it is enough just to send that one field via PATCH, instead of having to send the whole object in a PUT request. We will continue to support the current APIv2 until 31.5. 2024.
  

...

• 2N IP intercoms 2.35.x
• 2N Access Unit 2.35.x
• 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.5.1 (February 2023)

Please note that this version is a minor release, further to the release of version 2.5 in December 2022. It focuses on corrections and compatibility with the 2.38 FW version of the 2N OS, it introduces no new feature. 

Changelog 2.5.1

Corrections:

• Resolved issue with LDAP settings.
• Resolved issue with global time profiles. 

Updates:

...

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.5

...

.1 Firmware Support & Bugfix (February 2023)

Please note that this version is a minor release, further to the release of version 2.5 in December 2022. It focuses on corrections and compatibility with the 2.38 FW version of the 2N OS, it introduces no new feature. 

Changelog 2.5.1

Corrections:

• Resolved issue with LDAP settings.
• Resolved issue with global time profiles. 

Updates:

• New version of the USB driver with a new certificate valid until end of January 2024 has been added to this release.

2N® Access Commander version 2.5 (Beta November 2022, production December 2022)

2N® Access Commander version 2.5 introduces NTP server functionality whilst work continues on a new API and interface.

...

• 2N IP intercoms 2.33.x
• 2N Access Unit 2.33.x
• 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.4.1 (October 2022)

Changelog 2.4.1

Corrections:

• Resolved issue with configuring of devices' display when more than one device connected to Access Commander.
• Resolved problem with creating/updating an RFID card over LDAP.
• Resolved issue with company colors and email templates.
• Resolved issue with disabling user's door controller role.
• It is possible to sort the devices by FW version now.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.4

...

.1 Firmware Support & Bugfix (October 2022)

...

Changelog 2.4.1

Corrections:

• Resolved issue with configuring of devices' display when more than one device connected to Access Commander.
• Resolved problem with creating/updating an RFID card over LDAP.
• Resolved issue with company colors and email templates.
• Resolved issue with disabling user's door controller role.
• It is possible to sort the devices by FW version now.

2N® Access Commander version 2.4 (September 2022)

2N® Access Commander version 2.4 makes Attendance Monitoring available even for smaller installations, and introduces some minor features whilst work continues on a new API and interface.

...

• 2N IP intercoms 2.34.x
• 2N Access Unit 2.34.x
• 2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)

Changelog 2.3.1

Please note that this version is a minor release, further to the release of version 2.3 in April. It focusses on corrections and introduces no new features.

Corrections:

• System admin reverted to state where it does not consume any manager licenses
• Attendance management authorizations will be removed from users where an installation without the attendance management license is updated to a new version.
• Presence of a user is updated in presence list without need for page refresh
• Corrected timestamps of attendance records when exported to CSV

Changelog 2.3 

...

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.3.1 Firmware Support & Bugfix

Changelog 2.3.1

Please note that this version is a minor release, further to the release of version 2.3 in April. It focusses on corrections and introduces no new features.

Corrections:

• System admin reverted to state where it does not consume any manager licenses
• Attendance management authorizations will be removed from users where an installation without the attendance management license is updated to a new version.
• Presence of a user is updated in presence list without need for page refresh
• Corrected timestamps of attendance records when exported to CSV

2N® Access Commander version 2.3

Changelog 2.3 

2N^® Access Commander version 2.3 introduces a new access matrix for quick setup and audit of access permissions, allows backup and restore to be managed from the web GUI and introduces new user authorization settings for increased flexibility.

...

• 2N IP intercoms 2.33.x
• 2N Access Unit 2.33.x
• 2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)

Changelog 2.2

2N® Access Commander version 2.2 (Beta November 2021 - Production December 2021)

2N® Access Commander version 2.2 introduces support of QR codes as a user credential, enables core functions to be set in the GUI and extends the range of ways a door may be controlled.

The maximum PIN code length will change to 9 digits in this version. PIN codes of 10 digits or more will automatically be represented as a QR code after updating, although they may still be entered as PIN codes on a keypad. To avoid this behavior, ensure PIN codes are shorter than 10 digits

...

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2N® Access Commander version 2.2

Changelog 2.2

2N® Access Commander version 2.2 (Beta November 2021 - Production December 2021)

2N® Access Commander version 2.2 introduces support of QR codes as a user credential, enables core functions to be set in the GUI and extends the range of ways a door may be controlled.

New Features: 

• QR code support:
• QR codes may be attributed to users and visitors as access credentials, enabling simple and convenient access via supported devices.

• • Standard users or visitors may be allocated a QR code in place of a PIN code as an access credential
  • QR codes are automatically generated, based on a random 10 digit code
  • QR codes may be emailed directly to the user or visitor
  • The underlying 10 digit PIN may still be entered by keypad where QR code reading isn't possible
  • Requires IP Style to read the QR code

• Core setting availability in web GUI
• Installers previously needed to connect a monitor and keyboard to 2N® Access Commander box or to the server running 2N® Access Commander in order to enable remote access by SSH and manage several core settings. This is no longer necessary as these settings are now available directly in the web GUI.

...

The maximum PIN code length will change to 9 digits in this version. PIN codes of 10 digits or more will automatically be represented as a QR code after updating, although they may still be entered as PIN codes on a keypad. To avoid this behavior, ensure PIN codes are shorter than 10 digits

Support of QR code reading in IP Style requires firmware version 2.34, which may be released several weeks after Access Commander version 2.2

2N® Access Commander version 2.2 introduces support of QR codes as a user credential, enables core functions to be set in the GUI and extends the range of ways a door may be controlled.

New Features: 

• QR code support:
• QR codes may be attributed to users and visitors as access credentials, enabling simple and convenient access via supported devices.

• • Standard users or visitors may be allocated a QR code in place of a PIN code as an access credential
  • QR codes are automatically generated, based on a random 10 digit code
  • QR codes may be emailed directly to the user or visitor
  • The underlying 10 digit PIN may still be entered by keypad where QR code reading isn't possible
  • Requires IP Style to read the QR code

• Core setting availability in web GUI
• Installers previously needed to connect a monitor and keyboard to 2N® Access Commander box or to the server running 2N® Access Commander in order to enable remote access by SSH and manage several core settings. This is no longer necessary as these settings are now available directly in the web GUI.

• • SSH connection may be enabled or disabled directly in the web GUI
  • System time & date settings may be directly managed in the web GUI
  • Access Commander application network settings may be directly managed in the web GUI

...

• 2N IP intercoms 2.32.x
• 2N Access Unit 2.32.x
• 2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)

Changelog 2.1

2N^® Access Commander version 2.1 (Beta August 2021 - Production September 2021)

2N^® Access Commander 2.1 introduces powerful new features aimed at user management and controlling the flow of people.

New Features:

• Occupancy Management
• In the wake of the Covid-19 pandemic, managing the density of staff or visitors in different areas has become increasingly important to ensure their safety. The Occupancy Management feature in Access Commander empowers building admins with the ability to control occupancy in a flexible way.
  • Creation of new ‘Area restrictions’ section to accommodate Anti Pass-bask and Occupancy management.
  • Occupancy thresholds may be set for each area
  • Enforcement may be set to either deny access after threshold is reached, or just to log the event
  • New ‘Occupancy’ dashboard widget available
  • New ‘Occupancy limit reached’ notification added
• Visitor management
• Manage visitors more easily than ever before with this dedicated new section focused on visitor management. Issue credentials before they arrive for ‘self-serve’ access and easily track users who failed to return their access cards.
  • New section for enrolling visitors
  • PIN codes and License Plate numbers may now be attributed as credentials to allow access
  • PIN codes may be sent by customizable email directly to the visitor, prior to their visit
  • Unreturned cards are easily visible
  • New ‘Visitors’ dashboard widget available
• Access point support
• The introduction of ‘Access Points’ allows for more flexible access management. It enables more accurate monitoring of the flow of users between zones, and differing multi-factor authentication requirements between zones, where a single device is used to control movement through a door in both directions.
  • Admin may chose between using ‘devices’ or ‘Access Points’ (for installations where a single device controls movement through a door in both directions)
  • Access points may be assigned to zones, in place of devices
  • Access point labels introduced in device detail pages, zone ‘devices’ tab and access logs
  • A single access point may be blocked (for Occupancy Management), rather than the whole device
  • Please note that there are corresponding changes in the labelling of entry points, which are now called ‘Access Point 1’ and ‘Access Point 2’, rather than ‘Entry’ and ‘Exit’
• Support of groups in LDAP sync
• Where an LDAP compliant directory is used for user synchronization, the user’s groups may also be synchronized, making the management of users via such a directory even more streamlined and effective.
  • Users may be syncronised and automatically placed into the corresponding groups in Access Commander (provided they have been set up)
  • Group specific base DN option introduced
  • Nested groups supported

Improvements:

• Notes may now be saved for each user or visitor
• Support added for IP Style
• License plate number supported in CSV synchronization
• Message added for LDAP users to show why they can’t change UN/PW in Access Commander
• Paging, search and filtering optimisations to improve system performance

...

• Standard user can no longer see navigation menu collapse icon
• Wrong user icon in attendance log
• Anti pass-back failure alert corrected
• Access log sorting by groups/zones respected beyond 1st page
• SignalR Connection drop in Chrome after 5 minutes fixed

Required device firmware versions for full feature support

• 2N IP intercoms 2.33.x
• 2N Access Unit 2.33.x

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

• 2N IP intercoms 2.31.x
• 2N Access Unit 2.31.x
• 2N Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)

...

2N^® Access Commander 2.0 is a major new release which brings great changes to the user interface, as well as powerful new features and improvements. Along with these changes, the license model of Access Commander has also been changed. All users with existing licenses will be migrated to the appropriate new license automatically and free of charge, ensuring you continue to benefit from the same functionality.

WE RECOMMEND EXISTING USERS RENEW THEIR LICENSE WITHIN 5 MINUTES OF UPDATE

 New Features:

• License Plate Recognition
  • License plate numbers are now a natively supported credential type in 2N^® Access Commander
  • Works alongside Axis cameras featuring Artpec 6 or higher processors and the "Vaxtor VaxALPR on Camera v.2.2" ACAP (support of Axis License Plate Verifier coming soon too)
  • Means that access at a parking barrier can be granted simply by recognition of an authorised license plate
  • License plate snapshots are saved in logs
• New customisable dashboard and widgets
  • The dashboard has been entirely reimagined to offer immediate access to key functions via cutomisable widgets
  • Widgets loaded to the dashboard are customisable for each authorised user
  • They offer a range of functions, including: system resources, access control overview, license status, focused access logs, focused event logs, focused device states, door widget and lockdown widget
  • Concentrate only on the information you need surrounding the doors/states/events most critical to your role
• Door control and video stream view
  • The new 'door widget' allows you to focus on strategic doors (eg: main entry)
  • Via the door's widget, you may trigger door opening
  • Doors may also be 'held' for a chosen period of time to aid with maintenance, visits or evacuation
  • Where a camera is connected to the IP Intercom, you may also access its internal or external video stream
• Emergency lockdown
  • Site-wide instant lockdown can be implemented via the new icon in the app bar
  • Lockdown 'Areas' allow devices to be grouped into logical areas for more granular lockdown control of parts of a building only
• Collapsible sidebar
  • Sidebar menu may be fully revealed or collapsed
  • Use the screen space more efficiently
• New licensing model
  • Old license types of 5 devices, 25 user for Attendance Monitoring and Synchronisation by LDAP or CSV are replaced by a new model in 2N^® Access Commander 2.0
  • Old license types will be discontinued from May 31st 2021 and are not compatible with 2N^® Access Commander 2.0 or above
  • New licenses include free Basic license for up to 5 devices and 50 users, Advanced license for up to 30 devices and 300 users, Pro license for up to 100 devices and 1000 users, Unlimited license for unlimited doors and users

...

• Attendance records may now be bulk exported to PDF for hard copy printing
• Basic support of 2N^® IP Style
• 2N^® Access Commander box now set to automatically restart after unexpected power interruption
• Paging, search and filtering optimisations to improve system performance

...

• 2N^® Access Commander box factory reset showing invalid progress
• Presence list not alphabetically sorted if special characters used
• LDAP base DN is case sensitive
• No progress showing whilst distributing new firmware

...

• 2N IP intercoms 2.32.x
• 2N Access Unit 2.32.x

...

• 2N IP intercoms 2.30.x
• 2N Access Unit 2.30.x
• 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.1

Changelog 2.1

2N^® Access Commander version 2.1 (Beta August 2021 - Production September 2021)

2N^® Access Commander 2.1 introduces powerful new features aimed at user management and controlling the flow of people.

New Features:

• Occupancy Management
• In the wake of the Covid-19 pandemic, managing the density of staff or visitors in different areas has become increasingly important to ensure their safety. The Occupancy Management feature in Access Commander empowers building admins with the ability to control occupancy in a flexible way.
  • Creation of new ‘Area restrictions’ section to accommodate Anti Pass-bask and Occupancy management.
  • Occupancy thresholds may be set for each area
  • Enforcement may be set to either deny access after threshold is reached, or just to log the event
  • New ‘Occupancy’ dashboard widget available
  • New ‘Occupancy limit reached’ notification added
• Visitor management
• Manage visitors more easily than ever before with this dedicated new section focused on visitor management. Issue credentials before they arrive for ‘self-serve’ access and easily track users who failed to return their access cards.
  • New section for enrolling visitors
  • PIN codes and License Plate numbers may now be attributed as credentials to allow access
  • PIN codes may be sent by customizable email directly to the visitor, prior to their visit
  • Unreturned cards are easily visible
  • New ‘Visitors’ dashboard widget available
• Access point support
• The introduction of ‘Access Points’ allows for more flexible access management. It enables more accurate monitoring of the flow of users between zones, and differing multi-factor authentication requirements between zones, where a single device is used to control movement through a door in both directions.
  • Admin may chose between using ‘devices’ or ‘Access Points’ (for installations where a single device controls movement through a door in both directions)
  • Access points may be assigned to zones, in place of devices
  • Access point labels introduced in device detail pages, zone ‘devices’ tab and access logs
  • A single access point may be blocked (for Occupancy Management), rather than the whole device
  • Please note that there are corresponding changes in the labelling of entry points, which are now called ‘Access Point 1’ and ‘Access Point 2’, rather than ‘Entry’ and ‘Exit’
• Support of groups in LDAP sync
• Where an LDAP compliant directory is used for user synchronization, the user’s groups may also be synchronized, making the management of users via such a directory even more streamlined and effective.
  • Users may be syncronised and automatically placed into the corresponding groups in Access Commander (provided they have been set up)
  • Group specific base DN option introduced
  • Nested groups supported

Improvements:

• Notes may now be saved for each user or visitor
• Support added for IP Style
• License plate number supported in CSV synchronization
• Message added for LDAP users to show why they can’t change UN/PW in Access Commander
• Paging, search and filtering optimisations to improve system performance

Corrections:

• Standard user can no longer see navigation menu collapse icon
• Wrong user icon in attendance log
• Anti pass-back failure alert corrected
• Access log sorting by groups/zones respected beyond 1st page
• SignalR Connection drop in Chrome after 5 minutes fixed

Required device firmware versions for full feature support

• 2N IP intercoms 2.33.x
• 2N Access Unit 2.33.x

Minimum supported firmware versions (devices prior to these versions will not be synchronised with Access Commander)

• 2N IP intercoms 2.31.x
• 2N Access Unit 2.31.x
• 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.0

Changelog 2.0

2N^® Access Commander 2.0 is a major new release which brings great changes to the user interface, as well as powerful new features and improvements. Along with these changes, the license model of Access Commander has also been changed. All users with existing licenses will be migrated to the appropriate new license automatically and free of charge, ensuring you continue to benefit from the same functionality.

WE RECOMMEND EXISTING USERS RENEW THEIR LICENSE WITHIN 5 MINUTES OF UPDATE

 New Features:

• License Plate Recognition
  • License plate numbers are now a natively supported credential type in 2N^® Access Commander
  • Works alongside Axis cameras featuring Artpec 6 or higher processors and the "Vaxtor VaxALPR on Camera v.2.2" ACAP (support of Axis License Plate Verifier coming soon too)
  • Means that access at a parking barrier can be granted simply by recognition of an authorised license plate
  • License plate snapshots are saved in logs
• New customisable dashboard and widgets
  • The dashboard has been entirely reimagined to offer immediate access to key functions via cutomisable widgets
  • Widgets loaded to the dashboard are customisable for each authorised user
  • They offer a range of functions, including: system resources, access control overview, license status, focused access logs, focused event logs, focused device states, door widget and lockdown widget
  • Concentrate only on the information you need surrounding the doors/states/events most critical to your role
• Door control and video stream view
  • The new 'door widget' allows you to focus on strategic doors (eg: main entry)
  • Via the door's widget, you may trigger door opening
  • Doors may also be 'held' for a chosen period of time to aid with maintenance, visits or evacuation
  • Where a camera is connected to the IP Intercom, you may also access its internal or external video stream
• Emergency lockdown
  • Site-wide instant lockdown can be implemented via the new icon in the app bar
  • Lockdown 'Areas' allow devices to be grouped into logical areas for more granular lockdown control of parts of a building only
• Collapsible sidebar
  • Sidebar menu may be fully revealed or collapsed
  • Use the screen space more efficiently
• New licensing model
  • Old license types of 5 devices, 25 user for Attendance Monitoring and Synchronisation by LDAP or CSV are replaced by a new model in 2N^® Access Commander 2.0
  • Old license types will be discontinued from May 31st 2021 and are not compatible with 2N^® Access Commander 2.0 or above
  • New licenses include free Basic license for up to 5 devices and 50 users, Advanced license for up to 30 devices and 300 users, Pro license for up to 100 devices and 1000 users, Unlimited license for unlimited doors and users

Improvements:

• Attendance records may now be bulk exported to PDF for hard copy printing
• Basic support of 2N^® IP Style
• 2N^® Access Commander box now set to automatically restart after unexpected power interruption
• Paging, search and filtering optimisations to improve system performance

Corrections:

• 2N^® Access Commander box factory reset showing invalid progress
• Presence list not alphabetically sorted if special characters used
• LDAP base DN is case sensitive
• No progress showing whilst distributing new firmware

Required device firmware versions for full feature support

• 2N IP intercoms 2.32.x
• 2N Access Unit 2.32.x

Minimum supported firmware versions (devices prior to these versions will not be synchronised with 2N^® Access Commander)

• 2N IP intercoms 2.30.x
• 2N Access Unit 2.30.x
• 2N^® Indoor Touch 2.0: 4.3.x (devices running versions prior to this will be disabled in Access Commander)

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Changelog 1.17.0

## If Access Commander is updated before IP Intercom and Access Unit firmware 2.31.x is available then some newer functions may not be fully supported. Please note the minimum supported firmware in this version is 2.29.x. Please also note that the default 2N SMTP server will no longer be available in version 1.17.0. We suggest you ensure your own SMTP server settings are defined upon update, if you have not already done so, to ensure system and notification messages continue being sent##

...