Release Notes Endpoint Data Protection 24.0.3

Build Information

• Download: Marketplace
• Initial Build Version: 24.0.3.0

System Requirements and Deprecations

• Endpoint Data Protection 24.0.2 introduces a new software requirement for the Server, please refer to the System Requirements for additional information
• MySQL database is no longer supported since Endpoint Data Protection 24.0 and newer
• SQL Server 2012 and Windows 2012 R2 are no longer supported since Endpoint Data Protection 23.0.2
• Please review the Update Guide: Endpoint Data Protection for other important changes

Retirement of the EDP Extension 

We decided based on customer feedback and lower than expected adoption to shift the investment from the EDP UUX extension to features which will benefit a broader set of customers and provide greater value. This results in a discontinuation of the Unified User Experience for EDP Extension from version 25.0 onwards.

Logins with Active Directory Credentials

We are introducing Active Directory (AD) Integration feature, allowing administrators to log in to the console using their existing AD credentials. This streamlines access management, enhances security, and simplifies the authentication process by leveraging a centralized identity provider. Administrators can now use familiar AD credentials, eliminating the need to manage separate login details. To make it a bit clearer what is really being used, we have changed the label from Use EgoSecure Authentication to Use username and password. Whenever you have enabled the Use username and password checkbox and enter the credentials in the SamAccountName format like shown in the screenshot below, the login via Active Directory credentials is used. To perform the Authentication with Active Directory Credentials,  ensure the following:

• Configure an EgoSecure administrator or super administrator based on an Active Directory account
• The user accounts needs to have granted Access this computer from the network on the EgoSecure Server in the local security policies or Group Policies Objects (GPO) 
• Enabled HTTPS server and connecting components to connect the Console via SSL 
• Enabled Use username and password in the Console login dialog
• Type full username (domain\username) and password into the Console login dialog

EgoSecure Console 24.0 Update 3	EgoSecure Console 24.0 Update 2

If you want to deactivate the SSO authentication for your Endpoint Data Protection environment, then you can perform the following: 

• Open the Registry on your Endpoint Data Protection server
• Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EgoSecureServer\Parameters
• Create a new DWORD (32-bit) value named AllowSSOAuthentication and set 0 as value.

After that, when a user tries to log in with SSO, they get a "This authentication type is not allowed" error. 

Improved Synchronization with Microsoft Entra ID

We have significantly improved the performance of synchronizations with Microsoft Entra ID (formerly Azure Active Directory), especially for larger environments. Through technical optimizations, including the reorganization of API calls using Microsoft Graph, we have reduced synchronization times dramatically. In our test lab, which contains 100,000 records, synchronization now completes in less than 20 minutes, compared to the previous duration of up to 9 hours.

Additional Fixes and Improvements

• Updated Bitdefender SDK to 3.0.1.353
• Fixed an issue with permissions for Bluetooth Keyboards with Low Energy feature on Windows 11 devices
• Fixed an issue with some connections to Microsoft Entra ID when connecting through a proxy server
• Fixed an issue where a manual sync with directory services would display an incorrect number of groups, which would indicate that the exclude filters were not working properly
• Fixed an issue with incorrectly showing certificate export entry in the Revision log