AirLock 2.4 Release Notes

Updated on 02 Dec 2024
1 Minute to read

Print
Share
Dark
Light
PDF

Article summary

Did you find this summary helpful?

Thank you for your feedback

Release Date: December 2, 2024

IMPORTANT INFORMATION ABOUT THESE RELEASE NOTES
These notes are for the following Axiad product versions:
AirLock 2.4
If you have any questions about these features or want to request a more in-depth discussion about the best way to leverage them, then reach out to us at productmanagement@axiad.com.

AirLock 2.4.0

Features

Ref ID	Description
PM-8591	Operators can now define which authentication methods can bypass AirLock. By default, AirLock lets users in if they authenticated using Axiad ID (Push/OTP), a certificate, Windows Hello for Business, or the Microsoft Authenticator.

Enhancements

Ref ID	Description
PM-8592	Users are automatically redirected to AirLock if any of the certificates on any of their authentication devices are within the renewal period and must be updated. Devices that contain multiple certificates can now be recognized and prompted for update via AirLock. This applies to ANY inserted device, even if the user is not employing it for authentication. If the certificate is within the renewal window or expired, then the user will be redirected to AirLock to update it.
PM-8940	Operators can now allow specific users (in addition to groups) to bypass AirLock enforcement.
PM-9942	All deployed executables are digitally signed

Ref ID

Description

PM-8592

Users are automatically redirected to AirLock if any of the certificates on any of their authentication devices are within the renewal period and must be updated. Devices that contain multiple certificates can now be recognized and prompted for update via AirLock.

This applies to ANY inserted device, even if the user is not employing it for authentication. If the certificate is within the renewal window or expired, then the user will be redirected to AirLock to update it.

PM-8940

Operators can now allow specific users (in addition to groups) to bypass AirLock enforcement.

PM-9942

All deployed executables are digitally signed

Bug Fixes

Ref ID	Description
PM-7300	The correct AirLock version displays in Windows Program list.
PM-6779	AirLock checks the Windows edition to ensure that it has the required features to work and will cancel installation if unsupported to avoid user errors after a failed installation. AirLock requires the Enterprise edition, and Axiad supports all versions of Windows currently supported by Microsoft.
PM-4090	An empty "Immune Security IDs" list is allowed and will enforce AirLock for all users, as expected.
PM-7949	AirLock successfully detects smartcard login over RDP

Known Issues

Ref ID	Description	Workaround
PM-10109	WHFB login may fail if an empty VSC is present on the system.	Remove the empty VSC.

Was this article helpful?

What's Next

AirLock Enforcement Logic

Table of contents

AirLock 2.4.0