An upcoming update to DataMiner Cube, and the Cube start window in particular, will make it much easier to spot when a connection may not be fully secure. With clearer, browser-style warnings, you will be able to immediately see when an HTTP(S) connection deserves extra attention.
Importantly, this change is not about blocking users or making connections harder. In fact, the connection process has become more flexible. What will change is the way Cube communicates the security status of a connection, giving you clearer visual feedback when encryption or trust is missing.
When a connection is considered unsafe, the Cube start window will now display a padlock icon next to the cluster name. This can happen when a cluster uses HTTP instead of HTTPS, or when an HTTPS connection has certificate-related issues. Users can still connect as before, but they now receive a clear indication that the connection may not provide the level of security that is typically recommended.
Clearer warnings for users
The idea behind this change is simple: make security concerns more visible without adding new restrictions.
Hovering over the padlock or certificate link shows more information, helping you immediately understand what is going on and how you can improve your setup. These warnings are automatically updated whenever a cluster is added, edited, opened, or refreshed in the background.
When Cube is launched over an unsafe connection, an extra warning may also appear. This warning is intended to inform, not to prevent access. For HTTP connections, it will appear every time. For other types of issues, Cube remembers the user’s choice and does not repeatedly display the same prompt. The padlock icon, however, remains visible until the connection has been secured.
That added flexibility can be useful, but it does not remove the underlying security risk. For production environments, using HTTPS with a valid certificate remains the recommended approach.
Improvements behind the scenes
This update also includes a broader cleanup of the way Cube handles web communication with the DMA. While users may not immediately notice these changes, they help ensure more consistent behavior across different parts of the client.
Overall, this update focuses on visibility rather than restriction. You will be able to continue working as before, while receiving clearer indications when a connection deserves a closer look.
The change will become available in the upcoming DataMiner Cube releases 10.5.0 CU17, 10.6.0 CU5, and 10.6.8.
Looking for more details? Visit the DataMiner Cube release notes.