Postman Query catalogue call no longer works

[oliverbusch]

Current Behavior

The Postman POST call {{CONSUMER_MANAGEMENT_URL}}/v3/catalog/request delivers an error message

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

Expected Behavior

The provide the catalog data

Steps To Reproduce

Execute the postman Calls

{{PROVIDER_MANAGEMENT_URL}}/v3/assets
{{PROVIDER_MANAGEMENT_URL}}/v3/policydefinitions
{{PROVIDER_MANAGEMENT_URL}}/v3/contractdefinitions

and
{{CONSUMER_MANAGEMENT_URL}}/v3/catalog/request

Tested with the build from today (21.11.2024)

[oliverbusch]

Based on the discussion I've additionally tested with the following payloads.

{
    "@context": {
        "edc": "https://w3id.org/edc/v0.0.1/ns/"
    },
    "@type": "CatalogRequest",
    "counterPartyAddress":"http://alice-controlplane:8084/api/v1/dsp",
    "protocol": "dataspace-protocol-http",
    "querySpec": {
        "offset": 0,
        "limit": 50
    }
}

and

{
    "@context": {
        "edc": "https://w3id.org/edc/v0.0.1/ns/"
    },
    "@type": "CatalogRequest",
    "counterPartyAddress":"http://alice-controlplane:8084/api/v1/dsp",
    "protocol": "dataspace-protocol-http",
    "counterPartyId": "BPNL000000000001",
    "providerId": "BPNL000000000001",
    "querySpec": {
        "offset": 0,
        "limit": 50
    }
}

but I get still the following error

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

In the data and control plans I see no error messages.

In alice sts I've found the following error message

│ Nov 25, 2024 9:15:18 AM org.glassfish.jersey.internal.Errors logErrors                                                                                                                                                              │
│ WARNING: The following warnings have been detected: WARNING: The (sub)resource method createAccount in org.eclipse.edc.api.iam.identitytrust.sts.accounts.controller.StsAccountsApiController contains empty path annotation.       │
│ WARNING: The (sub)resource method updateAccount in org.eclipse.edc.api.iam.identitytrust.sts.accounts.controller.StsAccountsApiController contains empty path annotation.

[oliverbusch]

With this payload I get a result

{
  "@context": {
    "edc": "https://w3id.org/edc/v0.0.1/ns/"
  },
  "@type": "CatalogRequest",
  "counterPartyAddress": "{{PROVIDER_PROTOCOL_URL}}",
  "counterPartyId": "BPNL000000000001",
  "protocol": "dataspace-protocol-http",
  "querySpec": {
    "offset": 0,
    "limit": 50
  }
}

To fix the issue it's necessary to add the counterPartyId in the Body of the {CONSUMER_MANAGEMENT_URL}}/v3/catalog/request POST request.

[rafaelmag110]

@oliverbusch It seems you found the problem, and yes the counterPartyId has to be added as shown in the API Spec: https://app.swaggerhub.com/apis/eclipse-tractusx-bot/tractusx-edc/0.8.0#/Catalog%20V3/requestCatalogV3.

However, the error message could indeed state that property is missing. That is an issue to be addressed in the upstream EDC Connector repository.

Since you found the solution for your issue, can this be closed?

[oliverbusch]

@rafaelmag110 The bug should not be closed until the Postman collection managmeent_api_test.json working again and you can go through the whole process.

[AndrYurk]

Hello, I would like to investigate and fix this issue as a first contribution, please assign it to me.
Thanks in advance!