DSC v5.1.2 - Fixes & Maintenance

In CHANGELOG.md:

Fixed

• Fixed deletion of artifact data before the set time.
• Fixed tags with different descriptions in openapi schema.
• Fixed missing paging information in openapi schema.

Changed

• Increase postgresql version to 42.2.20.
• Increase spring-boot version to 2.5.1.

DSC v5.1.1 - Fix

In CHANGELOG.md:

Fixed

• Add missing hateoas information in openapi schema.

DSC v5.1.0 - Telemetry

In CHANGELOG.md:

Added

• Add telemetry collection via Jaeger.

Changed

• Replace deprecated JPA calls (getOne -> getById).
• Increase length restriction for URIs in database columns to 2048.
• Increase modelmapper version to 2.4.4.
• Increase equalsverifier version to 3.6.1.
• Increase spring-openApi-security version to 1.5.9.
• Increase spring-openapi-ui version to 1.5.9.
• Increase maven-javadoc-plugin version to 3.3.0.
• Increase spring-boot version to 2.5.0.
• Increase checkstyle version to 8.43.
• Increase pmd version to 6.35.0.
• Increase pitest version from 1.6.6 to 1.6.7.

Fixed

• Representations have now only one self-link.
• Set Basic Auth Header on (provider) backend calls.
• Ignore empty extension /** on GET **/artifacts/{id}/data/**.
• GET **/artifacts/{id}/data and POST **/artifacts/{id}/data will now return the same output.

DSC v5.0.2 - Fix

In CHANGELOG.md:

Changed

• Make the Clearing House url setting optional in application.properties.

Fixed

• Persist URIs as strings in database.

DSC v5.0.1 - Minor Changes

In CHANGELOG.md:

Changed

• H2 does not persist database to files.
• Change additional list mapping for received attribute list with a single item.
• Disable unused rolling file appender in log4j2.xml.

DSC v5.0.0 - Data Model

In v5.0, the entry point for the REST API can be found at /api and the Swagger UI can be accessed at /api/docs. Find our new documentation at https://international-data-spaces-association.github.io/DataspaceConnector/.

In CHANGELOG.md:

Added

• Partially support of HATEOAS.
• Add pagination for REST calls on resources.
• Integration and configuration of Jaeger for using open telemetry.
• Set default application name to Dataspace Connector in application.properties.
• Add custom spring banner.
• Add separate controller methods for each IDS message type.
• Add global exception handlers for ResourceNotFoundException, JsonProcessingException, and any
  RuntimeException.
• Add possibility to disable http tracer in application.properties.
• Add possibility to restrict depth of returned IDS information on DescriptionRequest.
  • Change IDS self-description to returning only a list of catalogs instead of their whole content.
  • Add possibility to send DescriptionRequestMessages for other elements than resources.
• Add remote IDs to each object for tracking origin.
• Support multiple policy patterns in one contract.
• Add Unit tests and integration tests.
• Add quality checks and project reports to pom.xml: execute with mvn verify site.
• Improve contract negotiation and usage control.
  • Add contract agreement validation in ContractAgreementHandler.
  • Note pre-defined providers for contract offers in ContractRequestHandler.
  • Use contract agreements for policy enforcement.
  • Handle out contract agreements for multiple artifacts (targets) within one negotiation sequence.
  • Restrict agreement processing to confirmed agreements.
  • Add relation between artifacts and agreements.

Changed

• Support of IDS Infomodel v4.0.4 (direct import in pom.xml).
• Change IDS Framework version to v4.0.7.
• Http tracer is limited to 10000 characters per log line.
• Log file creation is disabled by default.
• Move Swagger UI to /api/docs.
• Change response type from string to object.
• Use correct response codes as defined by RFC 7231.
• Replace old data model: catalogs, resources, representations, artifacts, contract, rules, and
  agreements.
  • Separate ResourceRepresentation into Representation and Artifact.
  • Separate ResourceContract into Contract and Rule.
  • Handle data in own database entity.
  • Separate management of resources and its relations.
  • Define clear interfaces between data model and the IDS Infomodel objects.
  • Add IDS object builder classes.
    • Build ids:Resource only if at least 1 representation and 1 contract is present.
    • Build ids:Representation only if at least 1 artifact is present.
    • Build ids:ContractOffer only if at least 1 rule is present.
  • Move remote information from BackendSource to Artifact.
• Strict implementation of model view controller pattern for data management.
  • Controller methods for resources and representations.
  • Provide strict access control to backend. Information can only be read and changed by services.
  • Strict state validation for entities via factory classes.
• Change IDS messaging sequence: Start with ContractRequestMessage for automated
  DescriptionRequestMessage and ArtifactRequestMessage.
• Improve data transfer.
  • Process bytes instead of strings.
  • Remove limit for data in internal database.
  • Establish connection via ArtifactRequestMessage for always pulling recent data.

Fixed

• Fix of buffer overflow in http tracer.
• Make message handler stateless.

Security

• Prevent leaking of technology stack in case of errors/exceptions.
• Logger sanitizes inputs to prevent CRLF injections.
• Mass Bindings.
• Timezone independence.

DSC v4.3.0 - Timeout Settings

In CHANGELOG.md:

Added

• Configure timeout values for http connections via application.properties.

DSC v4.2.0 - Conntector-restricted Data Usage

The connector supports a new IDS policy pattern: connector-restricted data usage. For each resource, you may specify one connector with it's id that should be able to request the data. Please find an example here.

In CHANGELOG.md:

Added

• New policy pattern: connector-restricted data usage.
• Validate CONNECTOR_RESTRICTED_USAGE on data request (as a provider).

DSC v4.1.0 - Query Resource & Automated Updates

In CHANGELOG.md:

Added

• Handle ResourceUpdateMessage: Update the local copy of resource upon receiving a ResourceUpdateMessage.
• Add attribute for endpoint documentation reference to ResourceMetadata.
• Store ownerURI, contractID, artifactID, and originalUUID in RequestedResource.
• Add support for query params, path variables, and additional headers when requesting artifacts.
• Add input validation for query params, path variables, and headers.
• Add usage control framework checking to the classes PolicyEnforcement and PolicyHandler.
• Add example files for deployment in Kubernetes.

Changed

• Configure Spring to fail on unknown properties in request bodies.
• Move settings for policy negotiation and allowing unsupported patterns to application.properties.
• Refactor HttpUtils to use the IDS Framework's HttpService.
• Add data string as request body instead of request parameter.

Fixed

• Exclusive use of the ConfigurationContainer for processing the connector's self-description and
  configurations to avoid state errors (relevant for the broker communication).

DSC v4.0.2 - Bugfix

In CHANGELOG.md:

Added

• Add message handler for ContractAgreementMessage.

Changed

• Answer with a MessageProcessedNotificationMessage to the consumer's ContractAgreementMessage.
• Save the ContractAgreement to the database and the Clearing House when the second
  AgreementMessage has been processed.
• Refine exception handling in the message building and sending process.
• Update from IDS Framework v4.0.2 to v4.0.3.

Fixed

• Send ContractAgreementMessage as request message.