v2.2.0

Service Versions (Image tags)

Helm Chart Versions

New Features

License Management

We have released a new service which delivers licensing to Glasswall Halo and allows you to access Glasswall Halo and Embedded Engine, it is now mandatory to provide a valid Glasswall license.

Introducing a new service: cdrplatform/license-management. This service serves as an API for managing active licenses and can be accessed through the main entry point into the cluster. The license management service focuses solely on license storage and does not impact the application of licenses within the cluster.

To enable your new license, follow the step-by-step instructions provided in the License Management Setup Guide.

File Cleanup

We have introduced a significant improvement in the handling of file cleanup. Previously, the responsibility for file cleanup was vested in the report aggregator, but with this release, we have introduced a dedicated service called cdrplatform/cleanup to handle the cleanup of transient files.

The new cdrplatform/cleanup service brings several benefits to our platform:

• Improved Performance: By offloading the file cleanup tasks to a dedicated service, the report aggregator can now focus solely on its primary function. This results in improved overall performance and reduced processing time for generating reports.

• Scalability: The new cleanup service is designed to be scalable, allowing it to handle increasing volumes of transient files efficiently, ensuring smooth operation even during peak usage periods.

• Centralised Management: With a dedicated cleanup service, we have a centralised and organised approach to managing file cleanup tasks, leading to better resource management and overall system stability.

To deploy this service please see our deployment documentation

Clean Room: Enhanced User Experience and New Features

With the release, we have several significant user experience (UX) improvements and exciting new features within Clean Room. This update aims to streamline your file processing and make the overall Clean Room experience smoother and more efficient.

New File Hash Retrieval

With this release, we introduce an essential capability to retrieve SHA256, SHA1, and MD5 file hashes directly from Clean Room for any processed file. This enhancement provides users with valuable cryptographic information, aiding in data integrity verification and security assessments.

Drag-and-Drop Support

The entire Clean Room user interface now supports file drag-and-drop functionality. You can simply drop files anywhere in Clean Room, not just in the designated drop zone. This improvement simplifies file loading, making it even more intuitive and user-friendly.

Enhanced Tablet Experience

Clean Room's tablet experience has undergone significant enhancements to provide a smoother user flow. The interface has been optimised to ensure seamless navigation and usability on tablet devices, empowering users to process files effortlessly, even on the go.

New Loading Screen

To add a touch of freshness and visual appeal, we have introduced a new loading screen for Clean Room. This screen will be displayed during the startup process.

Policy Management Integration

For users who have policy management configured, Clean Room now processes all files in relation to the default policy. This streamlines the file-handling process, ensuring consistency and adherence to predefined policies. For those without policy management, files will be processed based on the strictest policy available, maintaining the same level of security and compliance as in previous releases.

We highly recommend all users to upgrade to this latest version of Clean Room to take advantage of these new features and improvements. Your feedback has been invaluable in shaping this release, and we remain committed to enhancing your Clean Room experience with every iteration.

Engine Upgrade

This release marks a significant advancement as we have upgraded to the latest Glasswall Embedded Engine Release 5. With this upgrade, we aim to deliver enhanced security, improved performance, and an even better file-processing experience for our users.

Please see Release 5 release notes for more information

Policy Management

The following values are now required with any request under the ArchiveConfig section of the Content Management Policy

"ArchiveConfig": {
      "tif": 1,
      "svg": 1,
      "webp": 1,
    },

We hope these new features and enhancements enhance your overall experience with our product. We value your feedback and are committed to continuously improving our application to meet your evolving needs. If you have any questions or encounter any issues, please reach out to our support team.

Fixes

1. Resolved Issue: "Allowed" Files Inside Archives

In previous versions, there was an issue where allowed files within an archive were incorrectly marked as rebuilt. In this release, we have addressed this problem by introducing a new allowed section in the manifest.json file. Now, any allowed files present inside an archive will be appropriately listed in the manifest.json file, ensuring accurate tracking and reporting.

2. Resolved Issue: Incorrect Handling of Archive Flags for JPEG and TIFF Files

Previously when sending a JPEG or TIFF file within an archive through Glasswall Halo, with the archive flag set to anything other than "Sanitise," would not block the file as expected. With this release, we have fixed this issue, and now files will be correctly rebuilt, ensuring the desired behavior is achieved according to the specified archive flag.

3. Resolved Issue: Missing Session-ID Header in Response

Previously, when a session-id header was passed in the request, it was not being returned in the response headers. With the latest update, we have fixed this oversight, and the session-id header will now be properly returned in the response, facilitating better tracking and identification.

4. Resolved Issue: Handling of Empty Rebuilt Files

In earlier versions, when requesting a rebuilt file and encountering an error, an empty file would be returned, leading to confusion and potential data loss. In this release, we have improved the error handling process. Now, if there is an issue while requesting a rebuilt file, you will receive a more appropriate 500 status code along with a clear error message, allowing for better troubleshooting and resolution.

Known Issues

• When using the V2 endpoint for archive file type detection, the returned file type was erroneously displayed as "unknown" instead of "archive."

  • Impact: This issue affects users relying on accurate file type detection through the V2 endpoint for archives, as it may lead to incorrect categorization of files.

Documentation

API Documentation

Glasswall Documentation

Clean Room

Archive Support Documentation

Licensing Documentation