RN200929: Release Notes: Raynet One Technology Catalog 14.1.3447.108 [RTM]

New Features

• Fast and Accurate Global Search [RCAT-29] [RCAT-45]
• Machine Learning / Artificial Intelligence for Even Faster Data Processing [RCAT-46]
• Granular Settings for the End-of-Life and End-of-Extended-Support Data [RCAT-58] [ZEN-32236] [RCAT-147] [RCAT-154]
• Claims and Origins of Information [RCAT-116] [RCAT-115] [RCAT-58]
• Hardware Normalization Rules [RCAT-21]
• Review Features [RCAT-2] [ZEN-28755]
• UNSPSC Category Chooser Hardware [RCAT-5]
• Automated Fingerprint Processor [RCAT-22]
• Tabs Now Have Counters [RCAT-53]

Security Improvements

• We have made uploading user content (such as product logos) safer by analyzing the type of file being uploaded and only allowing files that are compatible with the intent. Non-image files, etc. are now rejected. [RCAT-26] [RCAT-12]
• Resolved an issue, where the /v1/tokensendpoint could return metadata of other tokens, even if the requesting user had was not their creator. [RCAT-59]
• The application now requires knowledge of the current password for the password change functionality. Previously, it was possible to set a new password without knowing the current password. [RCAT-39]

Other Improvements

• Improved the way the "latest" version is calculated. Previously, the algorithm might not have returned the latest version if some releases had an unknown release date AND did not have a consistent release pattern. This version handles this case better. [RCAT-25]
  • Additionally, some products could have returned a generic version "Any" instead of a specific version. This has also been fixed. [RCAT-139]
• The server application and its workers are now .NET 8. [RCAT-3]
• Several minor UI performance improvements by eliminating double superfluous calls. [RCAT-110]
• Added additional validation to prevent creation of publishers with duplicate names and removal of the name (when editing). Note that this behavior was already correctly protected in the UI, so this change only applies to API usage. [RCAT-93] [RCAT-94]
• API token creation via the API is now not allowed if the value of the token name is empty. [RCAT-140]
• Improved the default logging format for better consistency and readability. [RCAT-34]
• It is now possible to define a fallback publisher CPE string for products that are not assigned to a publisher. The input field for this can be found in the Product Edit dialog. [RCAT-36]
• Removing API tokens is now much faster (for tokens with a large usage footprint). [RCAT-134]
• Synchronization files are now treated as operations and can be tracked in the user interface (in the Operations view). [RCAT-95]

Resolved issues

• Resolved an issue where it was not possible to export fingerprints to CSV format. The export process was always stuck with an infinite progress bar. [RCAT-49] [ZEN-31072]
• Fixed incorrect behavior for instances receiving data from a parent instance. In case of a specific conflict where a software item was removed on the parent, some remnants at the fingerprint level were possible after synchronizations. The behavior in this new release is to return these fingerprints to the pool instead of assigning them to a deleted product/release. [RCAT-18] [ZEN-28679]
• Fixed an issue where it was not possible to browse the hardware products if the software products had a filter set on one of their specific properties, e.g. "Platform". This problem was caused by the same shared filter sets. In this release, software and hardware filters have their own separate settings. [RCAT-50]
• Resolved an issue where in some cases it was not possible to delete a user from an existing group. [RCAT-70]
• Resolved an issue where in rare cases, a specially crafted raw fingerprint data sent for recognition could return an error The recognition engine returned an error with code 0x003 from the recognition API. [RCAT-182]
• Fixed a subtle problem with calculating MD5 checksum hashes for raw data. Previously, the function was prone to fail due to thread safety issues. Under heavy load, when calculating a large number of fingerprints, this could lead to a collision of hashes, affecting subsequent recognitions. This could be observed by receiving sporadic mismatches between raw and normalized data. The algorithm has been improved and is no longer susceptible to this behavior. [RCAT-206]

Breaking changes

UI and front-end controls have been migrated to Angular 18. Note that this affects the list of supported web browsers (see https://angular.dev/reference/versions?utm_source=chatgpt.com#browser-support for more details). [RCAT-4] [RCAT-20]

• Chrome and other Chromium-based browsers (Edge, Opera, Vivaldi, Brave etc.): 2 most recent versions
• Mozilla Firefox: latest and extended support release (ESR)
• Apple Safari: 2 most recent major versions