Catalog non-accessible due to error while fetching client secret from vault

[joaoslva]

Hey! I'm having an issue while trying to access either Bob or Alice's catalogs.

Current behaviour

Basically there is no response being returned by the endpoint I'm querying to get the assets available in Bob's catalog. Bellow there is a print of the logs in Bob's control plane pod:

This error message keeps repeating over and over. The same goes for Alice's control plane, the only change is in the secret alias.

Steps to reproduce

Deploy the MXD like indicated in the README file, create an asset on Alice's side and then run this code snippet that I'm using in a Jupyter Notebook to check Bob's catalog:

    f"{bobUrl}/management/v3/catalog/request",
    json={
        "@context": {
            "@vocab": "https://w3id.org/edc/v0.0.1/ns/",
            "odrl": "http://www.w3.org/ns/odrl/2/",
        },
        "@type": "CatalogRequest",
        "counterPartyId": "BPNL000000000001",
        "counterPartyAddress": "http://alice-controlplane:8084/api/v1/dsp",
        "protocol": "dataspace-protocol-http",
        "querySpec": {
            "@type": "QuerySpec",
            "offset": 0,
            "limit": 50,
            "sortField": "http://purl.org/dc/terms/type",
            "sortOrder": "ASC",
        },
        "filterExpression": [
            {
                "operandLeft": "https://w3id.org/edc/v0.0.1/ns/id",
                "operator": "=",
                "operandRight": assetname,
            }
        ],
    },
    headers={"x-api-key": bobApiKey, "Content-Type": "application/json"},
)

bobUrl and assetname are predefined variables in my Notebook. It is expected to receive no response after running the snippet like what is happening on my side

[ndr-brt]

hey @joaoslva were you able to make it work?

[joaoslva]

Hi @ndr-brt! First of all, thank you for reminding me that I've opened this issue by replying!

Yes, I did manage to get it working by pulling an older commit instead of the most recent one from the repo. This solution came up because a colleague of mine was running the MXD example without any problem, but he hadn't pulled the code in a while. When he pulled the most recent version of the code (at the time, a few days after I've opened the issue), the same error started occurring on is side. We ended up pulling the commit that he previously had working fine on his machine. We haven't tested running the most recent code though

Not sure what the specific commit that is working for us is right now, but I can reach him to check with him which one were using, if that is still pertinent.

[ndr-brt]

We are aware the main branch is currently not stable, in fact there's a discussion opened to decide on how to make the MXD always usable.
#546

Will close this in the meantime