international-data-spaces-association / ids-deployment-examples Goto Github PK

As per the readme, after deploying the "full example", I try to access

Dataspace Connector Swagger UI: https://localhost:8080/api/docs

And I am getting back a 404. In general all endpoints in /api/ give back a 404.
Could you please advise?

Hello,
I never use create_resource.sh , start provider and consumer normal, and the offer can be checked by provider. But now hava a exception, consumer baunch negotiate a contract request, ‘ Could not find any matching contract offers for your request.' Request help on how to troubleshoot the problem, thanks.

Hello,

i have updated my IDS folder with the recent version,
i am trying the provider-consumer example.

Now i am not able to conclude the readme path, that was working before.

In the readme you are told to copy/paste the “permission” part and to change/add the “artifact ID”.
Somehow the “rule ID” was fix before it seems, because as already said I was able to get to the end of the readme example with the lower 5.x version.

Now after the update, the “rule ID” is not correct, as it makes sense due to the random created IDs by the connector and needs also to be replaced.

But now the issue is : “Received invalid agreement during negotiation phase.”

I double checked the IDs of all components by looking at the output of “create_resource.sh”
and rechecking the coresponding RESTcalls it in swagger.
They are all correct, nothing has been changed in the git clone.

What can I do?

Hello,

i have updated my IDS folder with the recent version,
i am trying the provider-consumer example.
Now i am not able to conclude the readme path, that was working before.

In the readme you are told to copy/paste the “permission” part and to change/add the “artifact ID”.
Somehow the “rule ID” was fix before it seems, because as already said I was able to get to the end with the lower 5.x version.

Now after the update, the “rule ID” is not correct and needs also to be replaced.

But now the issue is : “Received invalid agreement during negotiation phase.”

I double checked the IDs of all components by looking at the output of “create_resource.sh” and rechecking it in swagger.
They are all correct, nothing has been changed in the git clone.

What can I do?

Hi, it seems that some config.json are outdated. We tried to use following config, which seems not to be compatible with image 6.5.1 (we simply mounted the file into the docker container). We alternatively choose to use the config.json of current DSC-branch, which works well.

Describe the bug
I am using Dataspace Connector version 5.1.2 and I have followed the Documentation for the installation of the Dataspace Connector with maven, docker and kubernetes and i have found the following issues:

1. Link not available:
   In the Manual and Documentation of the Dataspace Connector section Deployment -> Build -> Profiles:
   The pom.xml provides three Maven profiles: no-documentation, no-tests, and release. The first one skips the Javadocs generation, the second one skips the execution of tests. The release profile shows all warnings and errors. To run a profile, please have a look at this guide.
   The link gives an ERROR 404 Page not found.
2. Plugins errors:
   • Spotbugs check is executed -> mvn spotbug:check
   Build failure. No plugin found for prefix ‘spotbug’ in the current project.
   • Statistics are generated -> mvn verify site
   There is a build failure, and the project statistics are not generated.
3. Docker installation error.
   It is not specified the docker version to launch the Dataspace Connector.
   We have used Docker version v20.10.7 and Docker-compose version 1.25.0
4. Kubernetes installation error: IDS-Deployment-Examples/dataspace-connector/slim/k8s at main · International-Data-Spaces-Association/IDS-Deployment-Examples (github.com)
   There is no guide for the installation of the required prerequisites (helm, minikube, git) I have followed the steps detailed at the end of this issue for the correct installation of the Dataspace Connector version 5.1.2.
   Also, at the subsection Install Steps -> Follow the instructions of the terminal for connecting to the service displayed in the terminal.
   The URL echo “Visit http://127.0.0.1:8080 to use your application” -> This URL is not accessible, instead it is https://localhost:8080/

For kubernetes I have followed this steps for the prerequisites installation:

The sample configuration of the full-example has default settings for proxies. Has to be checked whether these can be removed.

Update all DSC setup examples: increase version and provide appropriate config files.