The Dataspace Connector is an implementation of an IDS connector component following the IDS Reference Architecture Model. It integrates the IDS Information Model and uses the IDS Messaging Services for IDS functionalities and message handling. The core component in this repository provides a REST API for loading, updating, and deleting resources with local or remote data enriched by its metadata. It supports IDS conform message handling with other IDS connectors and components and implements usage control for selected IDS usage policy patterns.
The official Docker images of the Dataspace Connector can be found here.
For an easy deployment, make sure that you have Docker installed. Then, execute the following command:
docker run -p 8080:8080 --name connector ghcr.io/international-data-spaces-association/dataspace-connector:latest
If everything worked fine, the connector is available at https://localhost:8080/. The API can be accessed at https://localhost:8080/api. The Swagger UI can be found at https://localhost:8080/api/docs.
For certain REST endpoints, you will be asked to log in. The default credentials are
password. Please take care to change these when deploying and hosting the connector yourself!
For a more detailed explanation of deployment and configurations, see here.
Next, please take a look at our communication guide.
For verifying that you have received an official image from a trusted source, run:
cosign verify --key dsc.pub ghcr.io/international-data-spaces-association/dataspace-connector:latest
The Software Bill of Material (SBoM) for every Docker image is supplied as
SPDX-JSON and can be found by appending
-sbom to the
image tag. For example, the SBoM for
The SBoM can be pulled via tools like oras.
oras pull ghcr.io/international-data-spaces-association/dataspace-connector:latest-sbom -a
Before updating to a new major release, please read this guide!
The container architecture of the entire IDS Connector is made up of several components. Some of them are optional. At the center is the Dataspace Connector itself (connector core) with its connector data management. Optionally, the Dataspace Connector GUI can be used. Jaeger can be connected for displaying collected OpenTelemetry data. For the integration of IDS-Apps into the connector infrastructure, Portainer can be used to load IDS-Apps from an IDS-AppStore-Registry and manage them in the infrastructure. The actual data can be located both locally and externally. External IDS-Ecosystem components can be reached via IDS-Messages.
The Dataspace Connector is IDS ready and approved for IDS graduation scheme.
You are very welcome to contribute to this project when you find a bug, want to suggest an improvement, or have an idea for a useful feature. Please find a set of guidelines at the CONTRIBUTING.md and the CODE_OF_CONDUCT.md.
This project is currently no longer maintained but looking for new maintainers.
Applications for maintainers shall be directed to the International Data Spaces Association.
This project was previously maintained by Fraunhofer ISST and after that by sovity GmbH. Please do not approach former maintainers. If you have questions, plase open an issue / discussion for the community or approach the International Data Spaces Association.
Former maintainer, developer and contributer:
- Sebastian Opriel, sovity GmbH
- Tim Berthold, sovity GmbH
- Omar Silva, sovity GmbH
- Heinrich Pettenpohl, Fraunhofer ISST, project manager
- Julia Pampus, Fraunhofer ISST, lead developer
- Brian-Frederik Jahnke, Fraunhofer ISST
- Ronja Quensel, Fraunhofer ISST
- Erik van den Akker, Fraunhofer ISST
- Fabian Bruckner, Fraunhofer ISST
- Gökhan Kahriman, Fraunhofer ISST
- Haydar Qarawlus, Fraunhofer ISST
- Johannes Pieperbeck, Fraunhofer ISST
- Michael Lux, Fraunhofer AISEC
- René Brinkhege, Fraunhofer ISST
- Steffen Biehs, Fraunhofer ISST