XNAT 1.9.1 – 1.9.1.1 Release Notes
XNAT 1.9.1 is primarily a security patch release with minor functional improvements. This release follows the work in XNAT 1.9.0 with additional dependency updates. These updates are not nearly as impactful to the XNAT plugin ecosystem, as only minor updates to the XSync plugin are being released to correspond with this.
XNAT 1.9.1.1 is a single-line hotfix release that addresses a bug displaying plugin settings when 5 or more plugins are injecting content into that admin page.
Enable Control of Secondary Capture Handling
When DICOM data is imported, SOP Class UID is examined and any value matching the list specified in in the file primary-sops.txt will be treated as “primary” DICOM. It is placed in a resource folder with label DICOM and tag DICOM. Any other files are treated as secondary capture, and are typically placed in a resource folder with format DICOM and label secondary.
As detailed in XNAT-8219, we have introduced a new site configuration called separateSecondaryDicomOnArchive and set this to “true” by default to mirror existing behavior. However, if this is set to “false”, all incoming DICOM files for a given scan will be grouped together in a single DICOM resource directory.
Handle Migration of CT Scan Options Column
As part of the fix for XNAT-8143 in the 1.9.0 release, the CT Scan datatype table in postgres was modified to allow the History column to extend longer than VARCHAR would allow. However, this change was not being migrated for previous installations of XNAT. This migration must be handled by system admininstrators, but as of a new fix in XNAT-8205, we have added instructions as a statement in xdat.log that give you the implementation-specific SQL statements to run.
Dependency Updates
Continuing the work in the XNAT 1.9.0 release to address internal security scanning for CVEs and SAST practices, a number of dependency library updates were made. These changes had minimal impact on core plugins released by the XNAT team, but other developers may want to take note.
Dependency Library | Old Version | New Version in XNAT 1.9.1 |
|---|---|---|
activemq | 5.16.0 | 5.16.7 |
bouncycastle | 1.64 | 1.78.1 |
commons-compress | 1.24.0 | 1.26.0 |
commons-configuration2 | 2.1 | 2.10.0 |
eclipse-jgit | 4.5.4.201711221230-r | 5.13.3.202401111512-r |
logback-core | 1.2.12 | 1.2.13 |
redisson | 3.20.1 | 3.22.0 |
spring-framework | 5.3.31 | 5.3.39 |
spring-ldap | 2.4.1 | 2.4.2 |
spring-oauth2 | 2.5.0.RELEASE | 2.5.2.RELEASE |
spring-security | 5.7.11 | 5.7.12 |
tomcat-embed | 9.0.54 | 9.0.93 |
Other Critical Improvements and Bugfixes
Preferences & API Behaviors
XNAT-8000: Changes in project metadata were not being reflected in API calls
XNAT-8014: Set a default value of “false” for checksum creation config setting
XNAT-8198: Address a bug with getting and setting values in the Preferences API
Site Admin Improvements and Fixes
XNAT-8138: Address a bug where AuthMethod was being ignored when creating new users
XNAT-8160: Enable CRON jobs in the Event Service to run at shorter intervals
XNAT-8202: Remove log error in xapi.log when using the Create User form in the Admin UI
UI Fixes
XNAT-8098: Address bug causing duplicate custom form report tabs to display intermittently
XNAT-8120: Fix date reporting for user cache updates
XNAT-8158: Harmonize date filtering behavior on InsertDate search columns to be consistent with other date fields
XNAT-8159: Fix broken links to CRON notation reference in Admin UI helptext
XNAT-8218: Refactor form value displays on report pages to account for wide content
Related Issues with the XNAT 1.9.1 Release
The XSync Plugin 1.8.0 will not run with the dependency updates made in XNAT 1.9.1. Please use XSync version 1.8.1.