FAIR Data Services Version 1.44.0

Summary

This release contains some minor bug fixes and back end updates, changes in support of the upcoming Faceted Search feature, an improvement to FAIR-Camunda integration and an update to the way FAIR stores configuration values.

FAIR Configuration Update

FAIR configuration stores a variety of values for configuring different aspects of FAIR, such as the default roles or default catalogue definition. These were previously stored as strings with little validation when editing the values via the API. These have now been migrated to JSON to support more complex configuration and better validation. Previously requests to the FAIR PUT /configurations/default-approved endpoint would have been formatted:

`{
  "value": "true"
}`

Following this change, the request above would now be formatted:

`{
  "value": {
    "value": true
  }
}`

The FAIR Swagger docs have been updated to reflect this change and can be viewed here.

API Token Changes

FAIR release 1.43 introduced Keycloak into the user authentication process, as part of this expiry time on user access tokens was reduced to 5 minutes.

We recommend that users interacting with the API create a long life token for that purpose. Instructions on how to do this can be found here: The FAIR API.

Released features