AirLock 2.3 Release Notes
- 11 Jul 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
AirLock 2.3 Release Notes
- Updated on 11 Jul 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
AirLock 2.3
New Feature
Custom User-Agent
By default AirLock identities as a standard Chrome browser when interacting with an Identity Provider. With this release it can now identify as “AxiadAirlock” instead. This allows you to refine further your authentication flow, and enforce or bypass specific policies when a user is authenticating through AirLock.
NOTE
This option is exposed through a registry setting, and can pushed to existing deployment using GPOs. Updated administrative templates will be delivered alongside this release.
Enhancements
Support for ADFS 3.0 (Windows Server 2012)
AirLock can now be used in conjunction with this older version of ADFS. Windows Server 2012 is reaching end of life, and we therefore strongly urge you to upgrade to the latest version or to a more modern Identity Provider as soon as possible.
Updated prerequisites
AirLock now requires:
Visual C++ Redistributable 2019 (64-bit) or above (link)
Axiad WebPCSC component 1.5.5 or above installed (as Administrator/for all users)
Supported Operating Systems
The list of officially supported operating systems is now:
Microsoft Windows 10 Enterprise - 21H2, 22H2
Microsoft Windows 11 Enterprise - 21H2, 22H2
Bug Fixes
Ref ID | Description |
|---|---|
PM-6601 | Users will be able to issue devices in environments where the group policy “Prevent access to registry editing tools” is enforced. |
Patch Releases
Release | Ref ID | Type | Description |
|---|---|---|---|
2.3.1 | PM-7143 | Bug Fix | AirLock can successfully enter kiosk mode if IdP does not support CORS |
PM-6601 | Bug Fix | Portal extension loads correctly when the GPO settings are set to restrict registry access |
Was this article helpful?
