You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case a connection is established with a provider and Clearing House was enabled, a process creation message was already sent to the Clearing House. Thus, a valid connection, which was logged with the agreement ID of consumer/provider, exists.
In case the same resource is requested, it seems, that no new agreement is created, but the existing one is used. Nevertheless from the logs it seems, that it is tried to create a new process ID in Clearing House for the existing agreement ID, which ultimately results in a HTTP Status 400 from Clearing House with ids:RejectionMessage
Bug Report
Describe the bug
In case a connection is established with a provider and Clearing House was enabled, a process creation message was already sent to the Clearing House. Thus, a valid connection, which was logged with the agreement ID of consumer/provider, exists.
DataspaceConnector/src/main/java/io/dataspaceconnector/common/ids/message/ClearingHouseService.java
Line 132 in cff7d16
In case the same resource is requested, it seems, that no new agreement is created, but the existing one is used. Nevertheless from the logs it seems, that it is tried to create a new process ID in Clearing House for the existing agreement ID, which ultimately results in a HTTP Status 400 from Clearing House with
ids:RejectionMessage
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No new process is created, but the existing one is used. Maybe first, a clearingHouse query shall be conducted e.g, with https://github.com/International-Data-Spaces-Association/IDS-Messaging-Services/blob/e6da46cbcbbf55bd0cfe1388396d76ae7c67fee2/clearinghouse/src/main/java/ids/messaging/clearinghouse/ClearingHouseService.java#L180
Screenshots & Logs
Stakeholders to keep updated
@kragall @ip312 @dhommen @tmberthold @omarsilva1
The text was updated successfully, but these errors were encountered: