New parameter counterPartyId in EDC version 0.7.3

[ma3u]

Our support engineers faced many faulty EDC catalog requests with deprecated V2 with missing parameter counterPartyId.

Please ensure the EDC version 0.7.3 with following parameter:

• "counterPartyId": "providerId",

You will get the error message from Identity Wallet:

• [{"message":"Unable to obtain credentials: Empty optional","type":"BadGateway","path":null,"invalidValue":null}]

The EDC v2 should fail with a error message.

EDC version 0.7.4 Swagger API (0.7.3 swagger doesn't consist catalog API)

Swagger API for 0.7.4 isn't valid: in Line 486 Operations must have unique operationIds.

• operationId: getTransferState

[ma3u]

generated EDC version 0.7.3 doesn't consist the Catalog API:

[ma3u]

@lgblaumeiser can you take a look?

[lgblaumeiser]

@ma3u @pdrd

The property counterPartyId exists since 0.7.0. With version 0.7.3, the catalog api v3 has been added which results that v2 is deprecated. The corresponding issue as mentioned in the release notes of the upstream EDC version 0.7.1 is eclipse-edc/Connector#4211. It contains the deprecation declaration of the v2 apis.

So looking at what you describe, the remaining issue is, that the v2 version of the catalog request does not work anymore due to a protocol mismatch with the wallet. But v3 does work properly, right? Anything, I overlooked?