QC v23.12 Release Notes v1.0

Arqit QuantumCloud™

v23.12 Release Notes

© Arqit Limited

This document contains confidential and proprietary information, the copyright of which belongs to Arqit Limited and is intended only for the addressee to whom this copy has been supplied. The recipient will neither copy, distribute or otherwise use the information contained in this document for any purpose other than that for which it has been made available, nor permit anyone else to do the same without prior written authorisation from Arqit Limited. The recipient will be held liable for any wrongful disclosure or use of any information contained in this document by them, their officers or employees, or anyone else to whom they make the information available.

What’s new

Basic activity filtering

Console users can perform a basic filter on Activity events to identify those related to a particular user or device, or events with specific text in the event description.

Users navigating to the ‘Activity’ page will see a search box at the top left of the screen. Typing into this box will automatically filter results to events with a full or partial match in the title or various fields.

The search is ‘fuzzy’, so users are encouraged to experiment with specificity if unexpected results are returned. This fuzziness will be tuned in future releases.

Authentication key controls

System administrators can control the length of time device authentication keys are valid for within their tenant. After this time period, devices will need to re-authenticate in order to access any QuantumCloud™ services.

The time period can be set across the estate by navigating to the ‘Policies’ page and selecting the edit button for the ‘Default Device Authentication Policy’. Users can then type a value and choose the relevant units (minimum of 1 minute, max of 28 days).

More granular policies can be applied to OUs or devices by copying the ‘Default Device Authentication Policy’ instance, editing the value in each copy, then applying them as required.

Multi-factor Authentication

Customers can request multi-factor authentication to be switched on for their entire tenant by raising a service desk request. Following implementation, all users accessing the console will be required to register a device using a QR code, which can be scanned with MS Authenticator (or any similar application) to assist in setup. Users will then be required to enter a code from the app each time they log in to the console.

Changes

SDK updates

The SDKs have not been updated for this release. Partners and customers are advised to incorporate the latest (v23.10) SDKs into their apps and services.

Minor changes

No minor changes in this release.

Bug fixes

QC-5673 (QCPI/PaaS) Fixed an issue whereby users without permissions to edit Security Groups would see errors instead of the relevant groups in the ‘Security Group’ column in the ‘Devices’ table.

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

Some features are not yet available across the suite of SDKs, these are captured in the table below.