Release notes Tesorion Immunity

Immunity 2025.2 contains several new functionalities as well as updates and improvements that are not externally visible.

Principal new functionalities and changes

• When using the “reception”-pages, for creating activation codes outside of the regular Immunity web interface, it is now possible to allow bulk-creation of codes
• For several components of Immunity, where an authentication against Azure/Entra/OpenID take place, multiple tenants can now be used
• It is possible to have Immunity use the Microsoft Graph API / Exchange Online to send mail

Points of attention

• You might note a slight change in the looks of the Immunity webinterface due to a migration to Bootstrap 5, which involved quite some fixes by our frontend-developer.

Hardware support

• Netgear M4350-series switches are now supported
• TP-Link Omada (WLAN) is now supported
• Meraki MS-series switches are now supported
• Alcatel OmniSwitch 6360-series and 6560-series switches are now supported
• Support for several Fortigate FGT-models (WLAN) has been added
• Ubiquiti Unifi Access Points are now supported
• LAN-802.1X is now supported on Juniper EX 3400, EX 4100 and EX 4400 series switches

As usual, there are also several minor improvementsand bugfixes that are not explicitly listed.

‍

Immunity 2025.1 contains several new functionalities as well as updates and improvements that are not externally visible.

Principal new functionalities and changes

• Extended support for SurfWired where MAC-based authentications can also be checked against Surf’sRADIUS-servers in the normal MAC-based authentication flow
• Optimizations in the SNMP-daemon to better deal with simultaneous triggers to update trunk-ports (for connected Fat access points or Local LAN switches) and to better deal with unreachable/unresponsive devices upon startup.
• Automatic Host group selection, based on Azure group membership, when using Azure as an authentication backend on registration pages for end users.
• The underlying database system (PostgreSQL) has been updated to version 17.

Points of attention

• If you are receiving Syslog from the Immunity RADIUS-process, and are parsing that, then note that the field “Q-Qnid”, which holds the Incident ID is client has an active incident, has been renamed to “Q-Incident”.

Hardware support

• Aruba AP600-series access points are now supported.
• Aruba 9000-series Wireless Lan Controllers are now supported.
• Cambium XV2-23T access point is now supported.
• Juniper EX 4400-series switches are now supported.
• TP-Link SG3452P switch is now supported.

As usual, there are also several minor improvements and bugfixes that are not explicitly listed.

Immunity 2024.2 contains several new functionalities as well as updates and improvements that are not externally visible.

Principal new functionalities

• It is possible to have Immunity perform an Intune compliance check when providing access to MAC-addresses and accounts.
• To debug network issues between Immunity and managed network hardware (or other network infrastructure Immunity interfaces with), you can now perform pings and traceroutes from the Immunity web interface.
• OpenID-functionality has been extended to the additional “reception”-pages, for creating activation codes outside of the regular Immunity web interface.

Hardware support

• Support for the Aruba MC-VA was reintroduced

As usual, there are also several minor improvements and bugfixes that are not explicitly listed.

‍