Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DPP v4.0.0] Transfer issue parsing EDR in edc 0.7.3 in migration to /v3 api #390

Closed
matbmoser opened this issue Jul 22, 2024 · 5 comments · Fixed by #388
Closed

[DPP v4.0.0] Transfer issue parsing EDR in edc 0.7.3 in migration to /v3 api #390

matbmoser opened this issue Jul 22, 2024 · 5 comments · Fixed by #388
Assignees
Labels
bug Something isn't working
Milestone

Comments

@matbmoser
Copy link
Contributor

matbmoser commented Jul 22, 2024

Current Behavior

image
Getting all the time digital twin not found because transfer could not be started:

image

I could change the transfer status from "transfer.process.started" which was giving a "REQUESTED" status in the EDC:
image

And not callback endpoint was called.

Once I have changed to "transfer.process" I finally got a way forward and received and error:
image

Problems found:

  • Chart in v4.0.0 was incorrectly created, missing correct policy configuration:

Should be "odrl:use"

  • Process event shall be changed from transfer.process.started to transfer.process:

List<CallbackAddress> callbackAddresses = List.of(CallbackAddress.builder().transactional(false).uri(receiverEndpoint).events(List.of("transfer.process.started")).build());

It should also be added to the chart configuration...

Impact and actions

  • v4.0.1 Hotfix release is required
@matbmoser matbmoser added the bug Something isn't working label Jul 22, 2024
@matbmoser matbmoser added this to the v4.0.0 milestone Jul 22, 2024
@matbmoser
Copy link
Contributor Author

I have checked it and maybe it looks like the "transfer.process.started" still needs to be in place in order to receive the callback

@matbmoser
Copy link
Contributor Author

Ok i found that the problem is in the consortia env.
I also found a critical error:
image

@matbmoser
Copy link
Contributor Author

This is still a old logic implemented to parse the BPN from providers

@matbmoser
Copy link
Contributor Author

image
Ok i have found the problem and solve it. Now there is a new function called buildDspEndpoint that checks for trailling slashes and also concats the dsp endpoint

@matbmoser
Copy link
Contributor Author

Its solved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
1 participant