Release Notes Redtrust 4.42.1
04/17/2026
New features
| Description | Requires agent update? |
|---|---|
| The Windows Agent is now available as a native ARM64 build. | ✅ |
| Site groups in Policies now include an Advanced configuration section with a Mapped sites field. When a site grants access to multiple downstream sites after authentication — as is common with centralized authentication mechanisms such as AOC or izenpe — this field lets you list those host names and apply certificate use policies to each downstream site independently. | ✅ |
| The Sign API now includes default signing configuration management through new endpoints. | ➖ |
| The Sign API now includes new REST endpoints for digital signing of PDF files. You can configure the position and format of the visual signature, include a signature image, and select the pages on which it appears. | ➖ |
Enhancements to existing features
| Description | Requires agent update? |
|---|---|
| The partner configuration sections in the admin console include user experience improvements. | ➖ |
| The configuration for certificates requested through Firmaprofesional now incorporates changes to increase the security level. | ➖ |
warning
If you have the Firmaprofesional module, contact the support team before applying this update.
Bug fixes
| Description | Requires agent update? |
|---|---|
| Policy When conditions no longer throw an error when the start or end time has a null value. | ➖ |
| Role queries no longer throw an error when the user has a null role assigned. | ➖ |
| User groups are now correctly displayed alongside individual users in the policy list. | ➖ |
| Fixed an error in the consumer registration of the Agent API. | ➖ |
| The Firmaprofesional module now allows certificate requests in roles without backup download permissions. | ➖ |
| User groups assigned to roles now appear in the role list view. | ➖ |
| Minor corrections across various product modules to improve platform stability. | ➖ |
Known issues
The standard procedure no longer allows downgrading to earlier versions due to internal changes. Before applying the update, create a snapshot of the machine state and perform a backup using the administration console. Download the package and apply the OpenRDPv2.bin file to ensure emergency access if needed. After the server update, complete the process using the second package included in the ZIP file.