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.

Sign up for GitHub

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

Jump to bottom

consumer TransferProcess id is different from the correlationId (dataRequest.id) #2960

Closed
ndr-brt opened this issue May 11, 2023 · 0 comments · Fixed by #2971
Closed

consumer TransferProcess id is different from the correlationId (dataRequest.id) #2960

ndr-brt opened this issue May 11, 2023 · 0 comments · Fixed by #2971
Assignees
@ndr-brt
Labels
bug Something isn't working dataspace-protocol related to the dataspace protocol
Milestone
Milestone 9

Comments

@ndr-brt
Copy link
Member

ndr-brt commented May 11, 2023

Bug Report

Describe the Bug

consumer TransferProcess id is different from the correlationId (dataRequest.id)
for the new protocol, the two ids should be equal on the consumer side. (as done for the negotiation)
@ndr-brt ndr-brt added the bug Something isn't working label May 11, 2023
@ndr-brt ndr-brt added this to the Milestone 9 milestone May 11, 2023
@ndr-brt ndr-brt added the dataspace-protocol related to the dataspace protocol label May 11, 2023
@ndr-brt ndr-brt self-assigned this May 12, 2023
@ndr-brt ndr-brt mentioned this issue May 12, 2023
Merged
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ndr-brt ndr-brt

Labels
bug Something isn't working dataspace-protocol related to the dataspace protocol
Projects
None yet
Milestone
Milestone 9
Development

Successfully merging a pull request may close this issue.

fix: set id same as correlationId in consumer transfer process Think-iT-Labs/edc-connector
1 participant
@ndr-brt