Release 4.2.4
Fixed a bug with the generation of a Data Profile based on a file where the job was not completing successfully if the data file was not formatted properly
Added an option to the user profile page on the UI to allow the user to specify a blank value for the state field
Replaced the use of log4j-1 with reload4j to eliminate any concern regarding the vulnerabilities detected in log4j-1
Upgraded the version of the Postgres driver used by the application to a more recent version that is free from security vulnerabilities
Release 4.2.3
Applied a change to enforce the access permission that a user without the USERS_VIEW permission should not be able to view their own profile
Fixed a bug where disabling a user account through the UI would not actually disable the account
Made fixes to the PIX Feed v3 interface to ensure that the validation of identifiers doesn’t fail when identifiers are specified using the PIX/PDQv3 convention
Fixed the configuration of the deployment of the PIX/PDQ v3 interface to work properly when the interface is enabled
Upgraded the reference data lookup code to ensure the hibernate layer works properly with the version of Hibernate included in this release
Upgraded the version of Apache CXF used to eliminate any potential security vulnerabilities
Fixed the update of global identifiers assigned to records so that when an update changes the association between two clusters of records where each cluster also has manual links from an external source, the global identifiers are not updated correctly
Applied a validation check to prevent the search capability from allowing users to query for all records using the wildcard character
...