...

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

Corrections:

• Device monitoring upgrade issue fixed.

• Indoor Touch 2.0 proxy issue fixed.

• Resolved issue with imports from older Access Commander versions.

• Devices connectivity issues resolved.

Required device firmware versions for full feature support

• 2N IP intercoms 2.41.x

• 2N Access Unit 2.41.x

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

• 2N IP intercoms 2.36.x

• 2N Access Unit 2.36.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.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:

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

Corrections:

• Fixed issue with a device display configuration.
• Minor translation corrections.
• Resolved issue with BT pairing for users synchronized over FTP.
• Resolved issue with filtering in access logs.
• Corrected picture import.
• Corrected attendance intervals connection.
• LDAP synchronization and long distinguishedName resolved.
• Update over proxy issue resolved.

Required device firmware versions for full feature support

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

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

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

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

Changelog 2.5

New Features:

• NTP Server - 2N® Access Commander now offers NTP server functionality. This is especially useful in installations having no access to the internet - Access Commander may distribute its clock (either as a proxy to external NTP server or its own clock) to all 2N intercoms and access units on site. There is then no need to manage time on each device manually.

Corrections:

• Resolution of minor issues and imperfections in this version.

Required device firmware versions for full feature support

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

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

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

Changelog 2.4.0

New Features:

• Attendance Monitoring for Access Commander Basic
• Installations of 2N® Access Commander running the free ‘Basic’ license will now be able to add on the optional ‘Attendance Monitoring’ license, making attendance monitoring available to smaller sites with 5 or less devices and 50 or less users. (The ‘Basic & Attendance monitoring’ license must only be applied to Access Commander version 2.4 or superior)

• Ready for PICard secure credentials
• 2N’s access control solution will soon support credentials secured by a new standalone application. 2N PICard Commander will offer credential security built on MIFARE DESFire technology. 2N® Access Commander is ready to import the unique keys created in this standalone application, once it is released.

• Feedback form
• Feedback and ideas for improvements can now be provided directly within the application, allowing future development to more closely reflect the needs of daily users. Feedback can be provided by any Access Commander user with some management authorization (eg: user manager or access)

Corrections:

• Corrected loading of phone time profiles
• LDAP synchronization behavior
• Change of default password behavior

Required device firmware versions for full feature support

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

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

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

New Features: 

• Access Matrix
• Setting up and auditing of access permissions has been made much simpler and quicker thanks to the visual representation offered in the new access matrix.
  • Offers a single place where new zones and groups may be created, and where they may be combined with time profiles to create access rules
  • Allows quick auditing of existing rules in a single table
  • Users and devices can be filtered, allowing auditing of individual users access to individual doors

• Backup and restore 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 configure periodic backup or perform a restore. This is no longer necessary as these settings are now available directly in the web GUI.
  • SMB backup location may be set within web GUI, as well as backup period settings
  • Local storage may be set as the backup destination, allowing backups to be stored within the 2N^® Access Commander filesystem. These backups can be downloaded to the client machine directly via the web GUI
  • Transfer of database form another instance of 2N^® Access Commander may now be done within the web GUI
  • New ‘backup now’ function for ad-hoc backups

• New user authorizations and access to dashboard widgets
• User authorizations have been overhauled to accommodate recent new features and innovations such as dashboard widgets, door control and visitor management.
  • New ‘Visitor management’ and ‘Door control’ authorizations have been added
  • Admins may assign companies whose visitors can be managed by a Visitor manager
  • Admins may assign doors which can be controlled by a user with this authorization
  • Existing roles of Attendance, User and Access management now have access to a selected range of dashboard widgets which are relevant to their role/authorization level

Improvements:

• Support of upcoming IP Verso 2.0
• PIN codes up to 15 characters in length may be defined
• Previous state information relating to offline devices is no longer shown in the Device Monitoring table
• Password validation added when deleting a device
• Clarification of Multifactor Authentication texts
• Focus is automatically placed on first input in modal input box

Corrections:

• Attendance mode can now be disabled if user does not have access credential
• After change of device, any existing exceptions are now added to the new device
• Credentials removed from access log for non-admins/user managers
• Corrected log export for managers
• User manager can set one time password for users
• User import fixed where first card or switch code is empty

Required device firmware versions for full feature support

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

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

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

...

• More door control options

...

• The ways in which the operator may control a door are extended in this release, allowing greater flexibility and easier control in larger installations.

• • Door may be held open or door opening triggered from device detail page
  • Doesn't require door to have corresponding widget
  • Device monitoring page show's door held status

...

• Time profile for multi-factor authentication

• The admin may now govern the need for multi-factor authentication amongst a zone’s devices by a time profile. This enables more flexibility in security policy be enforcing heightened security only during critical times.

...

• • Multi-factor authentication options for a zone includes a time profile attribute
  • Outside the time profile, single-factor authentication is possible
  • Multi-factor authentication may still be applied continuously in a zone, without the condition of a time profile

...

• Template email management

...

• Emails containing user or visitor PIN codes or QR codes may be customised for each company, allowing for content to be tailored to the needs of a company and its brand.

...

• • Templates contain customisable header, introduction and additional message
  • Can be used to include information such as directions to a company
  • Includes customisable background and foreground color options
  • Templates may differ for each company

• Enforcement of valid device certificates

...

• To offer even greater security options, the admin may choose to enforce the use of valid certificates in devices to allow connection to Access Commander.

...

• • Toggle option added to enforce device certificate validation
  • Where enabled, Access Commander will only allow connection to devices with valid certificates

Improvements: 

• SMTP server certificate validation options added
• Database optimisations to improve system performance

Corrections:

• Attendance monitoring may now be activated for users who hold only Bluetooth credentials
• Holidays are now synchronized to lift devices
• CSV synchronisation now works during trial
• Corrected issue with door widget lockdown state in certain conditions
• Corrected function of deputy imported from a device
• System texts clarified or modified

Required device firmware versions for full feature support:

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

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

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

...