Arqit SKA-Platform PaaS Release v24.07
Details | |
---|---|
Release version | v24.07 |
Release Date | (features available from ~1900 BST) |
Published |
What’s new?
Customised ‘Activity status' boundaries
System administrators can customise the boundaries between the Green (Active), Amber (Recently active) and Red (Inactive) activity statuses via the administration console.
The time period for each status can be set across the estate by navigating to the ‘Policies’ page and selecting the edit button for the ‘Default Device Monitoring Policy’. Users can then edit the values and choose the relevant units for the upper boundaries of the Green and Amber statuses, (minimum of 1 minute, max of 7 days).
More granular policies can be applied to OUs or devices by copying the ‘Default Device Monitoring Policy’ instance, editing the values in each copy, then applying them as required.
Activity statuses are calculated from Heartbeat messages sent by devices to the platform. Devices not sending heartbeat messages will remain unaffected (the Activity status will remain Grey (Unknown)).
What’s changed?
The liboqs libraries used by the platform have been updated to v0.10.0. For more details, see https://github.com/open-quantum-safe/liboqs/releases/tag/0.10.0.
Known Issues
QC-2901 (QCPI/PaaS) Python SDK does not currently support Python v3.11. Support will be added in a future release. SDK developers are advised to use v3.10 of Python in the interim.
SDK feature matrix (SDKs v24.06)
Some features are not yet available across the suite of SDKs, these are captured in the table below.
Feature/SDK | Kotlin/Java | C++/C | Python |
QKEY registration | ✅ | ✅ | ✅ |
OTA_TLS registration | ✅ | ✅ | ✅ |
OTA__QUANTUM registration | ✅ | ✅ | ✅ |
Key negotiation via sockets | ✅ | ✅ | ✅ |
Key negotiation via MQTT | ✅ | ❌ | ✅ |
Device de-registration | ✅ | ✅ | ✅ |
Device recovery | ✅ | ✅ | ✅ |
Declaration of ‘Application Name’ | ✅ | ✅ | ✅ |
Registration configuration | ✅ | ✅ | ✅ |
Application heartbeat | ✅ | ✅ | ✅ |
Application properties | ✅ | ✅ | ✅ |
Device-based policies | ✅ | ✅ | ✅ |