Contract Agreement ID not received after contract negotiation

[Its-suLav-D]

Hey There,

Do the opposing Connector (Provider) have to accept the contract negotiation so I can get the contract agreement ID?

This is the response that I get once I negotiate the contract. Since my contractAgreementID is null my application keeps sending multiple request every sec. Can anyone provide any hint to solve the issue. I appreciate your response. Thanks a lot.

{
    "createdAt": 1667944128085,
    "updatedAt": 1667944129495,
    "contractAgreementId": null,
    "counterPartyAddress": "https://materialpass.int.demo.catena-x.net/provider/api/v1/ids/data",
    "errorDetail": null,
    "id": "7bf2f2f2-e298-4a2d-8b4e-cb470d0547b3",
    "protocol": "ids-multipart",
    "state": "REQUESTED",
    "type": "CONSUMER"
}

[Its-suLav-D]

@DominikPinsel Wondering if you could provide any hint on the issue. I appreciate your response. Thanks

[DominikPinsel]

As long as the contract agreement ID is null the negotiation is still in progress. In your case it is REQUESTED and your connector is waiting for the other connector to answer. If your negotiation state is not able to progress it could be, that the other connector is not answering. Reasons might be, that there is a configuration issue within the other connector. Or its also possible that there was something not correctly configured for your connector (could be DAPS or IDS webhook).

_{Dominik Pinsel [email protected], Mercedes-Benz Tech Innovation GmbH, legal info/Impressum}

[Its-suLav-D]

Thank you so much for the response. Just a quick follow up question. I was able to request the contract offer catalog from the product-battery-consumer demo URL(https://materialpass.int.demo.catena-x.net/provider/api/v1/ids/data) which is available in the repository, and this is the response that I got. Actually, I got two objects, but I removed one for the sake of simplicity.

{
    "id": "default",
    "contractOffers": [
        {
            "id": "1:20e3bef2-be80-4643-a86e-742f08cbd3d1",
            "policy": {
                "permissions": [
                    {
                        "edctype": "dataspaceconnector:permission",
                        "uid": null,
                        "target": "urn:uuid:61125dc3-5e6f-4f4b-838d-447432b97918",
                        "action": {
                            "type": "USE",
                            "includedIn": null,
                            "constraint": null
                        },
                        "assignee": null,
                        "assigner": null,
                        "constraints": [],
                        "duties": []
                    }
                ],
                "prohibitions": [],
                "obligations": [],
                "extensibleProperties": {},
                "inheritsFrom": null,
                "assigner": null,
                "assignee": null,
                "target": "urn:uuid:61125dc3-5e6f-4f4b-838d-447432b97918",
                "@type": {
                    "@policytype": "set"
                }
            },
            "asset": {
                "id": "urn:uuid:61125dc3-5e6f-4f4b-838d-447432b97918",
                "createdAt": 1668004741523,
                "properties": {
                    "asset:prop:byteSize": null,
                    "asset:prop:description": "Battery Passport test data",
                    "asset:prop:id": "urn:uuid:61125dc3-5e6f-4f4b-838d-447432b97918",
                    "asset:prop:fileName": null
                }
            },
            "assetId": null,
            "provider": "urn:connector:provider",
            "consumer": "urn:connector:consumer",
            "offerStart": null,
            "offerEnd": null,
            "contractStart": null,
            "contractEnd": null
        }, 
    ]
}

Just wondering if there was a configuration issue on my connector would I still get the 200 response?

Moreover, when I negotiate the contract, this is the payload that I attach with my request body

    const initiateRequest: NegotiationInitiateRequestDto = {
      connectorAddress: 'https://materialpass.int.demo.catena-x.net/provider/api/v1/ids/data',
  
      offer: {
        offerId: contractOffer.id,
        assetId: contractOffer.asset.id,
        policy: contractOffer.policy,
      },
      connectorId: 'foo',
      protocol: 'ids-multipart'
    };

I am wondering if this is because of connectorID ? I tried passing my ClientID, IDS WEB Hook address but still I get REQUESTED State. Any insights and hints are highly appreciated. Thanks a bunch.

[Its-suLav-D]

@DominikPinsel Would highly appreciate it if you could provide some feedback on your leisure. Thanks a lot 😊.

[DominikPinsel]

@Its-suLav-D
I assume there are two possibilities:

1. the other does not trust your connector
2. the other connector cannot answer your connector

So what are reason why the other connector does not trust your connector?

1. The two connectors have not configured the same DAPS.
2. The other connector has the wrong 'audience' configured.

What are reasons the other connector cannot answer your connector?

1. You have configured an invalid URL in ids.webhook.address
2. Your connector is not reachable from the internet, maybe your Kubernetes/Ingress/Service/etc. is not configured correctly.

You can test it by calling the URL configured in ids.webhook.address with

curl --location --request POST 'https://connector.com/api/v1/ids/data' \
--form 'header="{
    \"@context\": \"https://w3id.org/idsa/contexts/context.jsonld\",
    \"@type\": \"ids:DescriptionRequestMessage\",
    \"modelVersion\": \"4.1.0\",
    \"ids:issued\": {
        \"@value\": \"2019-12-21T13:32:33.073+02:00\",
        \"@type\": \"http://www.w3.org/2001/XMLSchema#dateTimeStamp\"
    },
    \"ids:issuerConnector\": {
        \"@id\": \"https://connector.cx-rel.edc.aws.bmw.cloud/BPNL000000000000/api/v1/ids/data\"
    },
    \"ids:senderAgent\": {
        \"@id\": \"http://example.org#connector\"
    },
    \"ids:requestedElement\": {
        \"@id\": \"http://example.org/some-URI\"
    },
    \"@id\": \"https://w3id.org/idsa/autogen/selfDescriptionRequest/b0731661-7df1-43e5-bb75-50f0709f31c9\"
}"' \
--form 'payload=""'

This is an IDS message without valid authentication, so your request will be rejected. But you should receive an answer.
Your ids.webhook.address setting should look like this http://connector.com

_{Dominik Pinsel [email protected], Mercedes-Benz Tech Innovation GmbH, legal info/Impressum}

[Its-suLav-D]

Thanks Mr. Dominik. This definitely helped.