"Could not find any matching contract offers for your request." error

[hoangkhuong272]

Dear,

I have 2 connectors as follows:
Provider: https://localhost:8080/api
Consumer: https://localhost:9999/api

At consumer, when request self-description of provider, response as follows:
{
"@context" : {
"ids" : "https://w3id.org/idsa/core/",
"idsc" : "https://w3id.org/idsa/code/"
},
"@type" : "ids:ResourceCatalog",
"@id" : "https://localhost:8080/api/catalogs/8d8c0b44-32e7-4a4e-a1b6-442a7e442547",
"ids:offeredResource" : [ {
"@type" : "ids:Resource",
"@id" : "https://localhost:8080/api/offers/dacf74cc-39d5-4bfe-a250-97c9672f3dd0",
"ids:standardLicense" : {
"@id" : "http://opendatacommons.org/licenses/odbl/1.0/"
},
"ids:resourceEndpoint" : [ {
"@type" : "ids:ConnectorEndpoint",
"@id" : "https://w3id.org/idsa/autogen/connectorEndpoint/2678e321-699b-48d2-a709-270fa6b20a64",
"ids:endpointDocumentation" : [ {
"@id" : "https://example.com"
} ],
"ids:accessURL" : {
"@id" : "https://localhost:8080/api/offers/dacf74cc-39d5-4bfe-a250-97c9672f3dd0"
}
} ],
"ids:contractOffer" : [ {
"@type" : "ids:ContractOffer",
"@id" : "https://localhost:8080/api/contracts/c94c414e-2628-4da0-a421-ff8ad49a1985",
"ids:contractStart" : {
"@value" : "2021-07-19T10:02:30.057Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
},
"ids:contractEnd" : {
"@value" : "2022-07-19T09:41:47.737Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
},
"ids:contractDate" : {
"@value" : "2021-07-21T02:38:44.159Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
},
"ids:prohibition" : [ ],
"ids:obligation" : [ ],
"ids:provider" : {
"@id" : "Hitachi"
},
"ids:permission" : [ {
"@type" : "ids:Permission",
"@id" : "https://localhost:8080/api/rules/3b4e08b8-e628-41df-b4c0-494efae0952a",
"ids:action" : [ {
"@id" : "https://w3id.org/idsa/code/USE"
} ],
"ids:description" : [ {
"@value" : "provide-access",
"@type" : "http://www.w3.org/2001/XMLSchema#string"
} ],
"ids:title" : [ {
"@value" : "Allow Data Usage",
"@type" : "http://www.w3.org/2001/XMLSchema#string"
} ]
} ],
"ids:consumer" : {
"@id" : "Hitachi"
}
} ],
"ids:representation" : [ {
"@type" : "ids:Representation",
"@id" : "https://localhost:8080/api/representations/913a890b-6b89-43bf-9f75-7841a3c912ae",
"ids:modified" : {
"@value" : "2021-07-19T10:40:35.265Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
},
"ids:mediaType" : {
"@type" : "ids:IANAMediaType",
"@id" : "https://w3id.org/idsa/autogen/iANAMediaType/32cf8dea-4691-4331-8ce3-641301451fd7",
"ids:filenameExtension" : "text"
},
"ids:language" : {
"@id" : "https://w3id.org/idsa/code/EN"
},
"ids:created" : {
"@value" : "2021-07-19T10:40:35.265Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
},
"ids:representationStandard" : {
"@id" : "json"
},
"ids:instance" : [ {
"@type" : "ids:Artifact",
"@id" : "https://localhost:8080/api/artifacts/ae3ac9dd-9915-476b-a6cc-ba055ff15ac8",
"ids:fileName" : "weather data",
"ids:byteSize" : 0,
"ids:checkSum" : "0",
"ids:creationDate" : {
"@value" : "2021-07-19T10:30:58.535Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
}
} ]
} ],
"ids:keyword" : [ {
"@value" : "weather",
"@language" : "EN"
}, {
"@value" : "data",
"@language" : "EN"
}, {
"@value" : "sample",
"@language" : "EN"
} ],
"ids:modified" : {
"@value" : "2021-07-19T07:26:38.703Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
},
"ids:description" : [ {
"@value" : "This is an example resource containing weather data.",
"@language" : "EN"
} ],
"ids:language" : [ {
"@id" : "https://w3id.org/idsa/code/EN"
} ],
"ids:version" : "1",
"ids:created" : {
"@value" : "2021-07-19T07:26:38.703Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
},
"ids:title" : [ {
"@value" : "Sample Resource",
"@language" : "EN"
} ],
"ids:publisher" : {
"@id" : "https://openweathermap.org/"
},
"ids:sovereign" : {
"@id" : "https://openweathermap.org/"
},
"key" : "value"
} ]
}

It seems above is a complete offer.
But when Negotiate a Contract Agreement from consumer as follows:

The request payload as follows:
[
    {
      "@type" : "ids:Permission",
      "@id" : "https://localhost:8080/api/rules/3b4e08b8-e628-41df-b4c0-494efae0952a",
      "ids:description" : [ {
        "@value" : "provide-access",
        "@type" : "http://www.w3.org/2001/XMLSchema#string"
      } ],
      "ids:title" : [ {
        "@value" : "Allow Data Usage",
        "@type" : "http://www.w3.org/2001/XMLSchema#string"
      } ],
      "ids:action" : [
        "@id" : "https://w3id.org/idsa/code/USE"
      ],
      "ids:target": "https://localhost:8080/api/artifacts/ae3ac9dd-9915-476b-a6cc-ba055ff15ac8"
    }
]

The response is NOT_FOUND as follows

The log at consumer:
2021-07-27T09:50:00,951 [https-jsse-nio-9999-exec-4] ERROR - JWT strings must contain exactly 2 period characters. Found: 0
2021-07-27T09:50:00,952 [https-jsse-nio-9999-exec-4] WARN - Could not parse jwt!
2021-07-27T09:50:00,954 [https-jsse-nio-9999-exec-4] WARN - TEST_DEPLOYMENT: IDS-Message is sent without a valid DAT, will not be send in PRODUCTIVE_DEPLOYMENT, reason: Mandatorily required information of the connector certificate is missing (AKI/SKI)!
2021-07-27T09:50:01,040 [https-jsse-nio-9999-exec-4] ERROR - JWT strings must contain exactly 2 period characters. Found: 0
2021-07-27T09:50:01,041 [https-jsse-nio-9999-exec-4] WARN - Could not parse jwt!
2021-07-27T09:50:01,043 [https-jsse-nio-9999-exec-4] WARN - TEST_DEPLOYMENT: IDS-Message is sent without a valid DAT, will not be send in PRODUCTIVE_DEPLOYMENT, reason: Mandatorily required information of the connector certificate is missing (AKI/SKI)!
2021-07-27T09:50:01,125 [https-jsse-nio-9999-exec-4] DEBUG - Built request message. [body=(okhttp3.MultipartBody@1dc8a037)]
2021-07-27T09:50:01,125 [https-jsse-nio-9999-exec-4] DEBUG - Built request message. [body=(okhttp3.MultipartBody@1dc8a037)]
2021-07-27T09:50:01,136 [https-jsse-nio-9999-exec-4] INFO - URL is valid: https://localhost:8080/api/ids/data
2021-07-27T09:50:01,137 [https-jsse-nio-9999-exec-4] INFO - Ok Http Client Protocols[h2, http/1.1]
2021-07-27T09:50:01,138 [https-jsse-nio-9999-exec-4] INFO - Ok Http Client Protocols[h2, http/1.1]
2021-07-27T09:50:01,139 [https-jsse-nio-9999-exec-4] INFO - Request is HTTPS: true
2021-07-27T09:50:01,783 [https-jsse-nio-9999-exec-4] INFO - {\n "@context" : {\n "ids" : "https://w3id.org/idsa/core/",\n "idsc" : "https://w3id.org/idsa/code/"\n },\n "@type" : "ids:RejectionMessage",\n "@id" : "https://w3id.org/idsa/autogen/rejectionMessage/cf112401-9448-41ba-b668-17e50dbb4b98",\n "ids:rejectionReason" : {\n "@id" : "https://w3id.org/idsa/code/NOT_FOUND"\n },\n "ids:correlationMessage" : {\n "@id" : "https://INVALID"\n },\n "ids:issuerConnector" : {\n "@id" : "https://w3id.org/idsa/autogen/baseConnector/7b934432-a85e-41c5-9f65-669219dde4ea"\n },\n "ids:senderAgent" : {\n "@id" : "https://w3id.org/idsa/autogen/baseConnector/7b934432-a85e-41c5-9f65-669219dde4ea"\n },\n "ids:securityToken" : {\n "@type" : "ids:DynamicAttributeToken",\n "@id" : "https://w3id.org/idsa/autogen/dynamicAttributeToken/b0568424-275c-4275-afa5-97669070d53c",\n "ids:tokenValue" : "rejected!",\n "ids:tokenFormat" : {\n "@id" : "https://w3id.org/idsa/code/JWT"\n }\n },\n "ids:modelVersion" : "4.1.0",\n "ids:issued" : {\n "@value" : "2021-07-27T02:49:58.073Z",\n "@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"\n }\n}
2021-07-27T09:50:01,809 [https-jsse-nio-9999-exec-4] INFO - Received response passed SHACL Validation.
2021-07-27T09:50:01,842 [https-jsse-nio-9999-exec-4] ERROR - [line: 1, col: 6 ] Unrecognized token 'Could': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
2021-07-27T09:50:01,844 [https-jsse-nio-9999-exec-4] WARN - Could not deserialize Playload The message is no valid JSON-LD and therefore could not be parsed.
2021-07-27T09:50:01,845 [https-jsse-nio-9999-exec-4] WARN - Skipping Connector-SecurityProfile Attribute!
2021-07-27T09:50:01,901 [https-jsse-nio-9999-exec-4] WARN - Received unexpected response message. [response=({reason=https://w3id.org/idsa/code/NOT_FOUND, payload=Could not find any matching contract offers for your request., type=class de.fraunhofer.iais.eis.RejectionMessageImpl})]
2021-07-27T09:50:01,901 [https-jsse-nio-9999-exec-4] WARN - Received unexpected response message. [response=({reason=https://w3id.org/idsa/code/NOT_FOUND, payload=Could not find any matching contract offers for your request., type=class de.fraunhofer.iais.eis.RejectionMessageImpl})]

No log appear at provider.

Are parameters wrong?
Or any missing info in provider's offer?

Thank you very much for your support.

[quangtinhle]

Hi Khuonghoang272,

I'm also learning about DSC and have some of the same problems as you.
Could you give me your contact information so we can discuss the matter in more detail.

Thank you.
Tinh

[hoangkhuong272]

Hi,

I may ask what is response in log

{
"@context" : {
"ids" : "https://w3id.org/idsa/core/",
"idsc" : "https://w3id.org/idsa/code/"
},
"@type" : "ids:RejectionMessage",
"@id" : "https://w3id.org/idsa/autogen/rejectionMessage/6140795b-76d7-488c-b0b6-068379175b33",
"ids:rejectionReason" : {
"@id" : "https://w3id.org/idsa/code/NOT_FOUND"
},
"ids:issuerConnector" : {
"@id" : "https://w3id.org/idsa/autogen/baseConnector/7b934432-a85e-41c5-9f65-669219dde4ea"
},
"ids:modelVersion" : "4.1.0",
"ids:senderAgent" : {
"@id" : "https://w3id.org/idsa/autogen/baseConnector/7b934432-a85e-41c5-9f65-669219dde4ea"
},
"ids:securityToken" : {
"@type" : "ids:DynamicAttributeToken",
"@id" : "https://w3id.org/idsa/autogen/dynamicAttributeToken/05b850be-2541-476e-95a8-dd03be5743cd",
"ids:tokenValue" : "rejected!",
"ids:tokenFormat" : {
"@id" : "https://w3id.org/idsa/code/JWT"
}
},
"ids:correlationMessage" : {
"@id" : "https://INVALID"
},
"ids:issued" : {
"@value" : "2021-08-11T08:48:18.084Z",
"@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"
}
}

I am testing in TEST_DEPLOYMENT mode. Do I need a valid DAT?

I notice that in error above when calling api/ids/contract at consumer, it seems the message did not go to provider (no log occurred at provider).
Could you please help what I need to check in this case?

Thanks,
Khuong

[gonzalogil26]

Hi Hoangkhuong272,

Have you already solved this issue?
The same happens to me and I was wondering if someone could help me.
It seems that all is correctly configured and the POST correctly made. However I receive the following ERROR:

2021-09-27T08:47:43,259 [https-jsse-nio-8080-exec-5] INFO - URL is valid: https://ids-dataprovider.tekniker.es:8080/api/ids/data
2021-09-27T08:47:43,260 [https-jsse-nio-8080-exec-5] INFO - Ok Http Client Protocols[h2, http/1.1]
2021-09-27T08:47:43,260 [https-jsse-nio-8080-exec-5] INFO - Ok Http Client Protocols[h2, http/1.1]
2021-09-27T08:47:43,260 [https-jsse-nio-8080-exec-5] INFO - Request is HTTPS: true
2021-09-27T08:47:43,463 [https-jsse-nio-8080-exec-5] INFO - {\n "@context" : {\n "ids" : "https://w3id.org/idsa/core/",\n "idsc" : "https://w3id.org/idsa/code/"\n },\n "@type" : "ids:RejectionMessage",\n "@id" : "https://w3id.org/idsa/autogen/rejectionMessage/365a3c86-f8a2-4902-98d8-39538187ac25",\n "ids:rejectionReason" : {\n "@id" : "https://w3id.org/idsa/code/NOT_FOUND"\n },\n "ids:securityToken" : {\n "@type" : "ids:DynamicAttributeToken",\n "@id" : "https://w3id.org/idsa/autogen/dynamicAttributeToken/4cf74b30-32b0-4d29-8cca-6ed58cc23a86",\n "ids:tokenValue" : "rejected!",\n "ids:tokenFormat" : {\n "@id" : "https://w3id.org/idsa/code/JWT"\n }\n },\n "ids:issued" : {\n "@value" : "2021-09-27T08:47:43.417Z",\n "@type" : "http://www.w3.org/2001/XMLSchema#dateTimeStamp"\n },\n "ids:modelVersion" : "4.0.0",\n "ids:recipientConnector" : [ ],\n "ids:correlationMessage" : {\n "@id" : "https://INVALID"\n },\n "ids:issuerConnector" : {\n "@id" : "https://w3id.org/idsa/autogen/baseConnector/7b934432-a85e-41c5-9f65-669219dde4ea"\n },\n "ids:senderAgent" : {\n "@id" : "https://w3id.org/idsa/autogen/baseConnector/7b934432-a85e-41c5-9f65-669219dde4ea"\n },\n "ids:recipientAgent" : [ ]\n}
2021-09-27T08:47:43,484 [https-jsse-nio-8080-exec-5] INFO - Received response passed SHACL Validation.
2021-09-27T08:47:43,522 [https-jsse-nio-8080-exec-5] ERROR - [line: 1, col: 6 ] Unrecognized token 'Could': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
2021-09-27T08:47:43,523 [https-jsse-nio-8080-exec-5] WARN - Could not deserialize Playload The message is no valid JSON-LD and therefore could not be parsed.
2021-09-27T08:47:43,523 [https-jsse-nio-8080-exec-5] WARN - Skipping Connector-SecurityProfile Attribute!
2021-09-27T08:47:43,575 [https-jsse-nio-8080-exec-5] WARN - Received unexpected response message. [response=({reason=https://w3id.org/idsa/code/NOT_FOUND, payload=Could not find any matching contract offers for your request., type=class de.fraunhofer.iais.eis.RejectionMessageImpl})]

I am also testing in TEST_DEPLOYMENT mode.

Thanks,
Gonzalo

[hoangkhuong272]

Hi @gonzalogil26,

I think there was something wrong during offered resource creation. I created offered resource step by step manually, when using /api/ids/description to request resource catalog information, the response looks fine, include contract, rule, artifact... (please see description of this ticket)

Then I used python script (under script folder) to create offered resource, I am able to negotiate the contract aggreement. So I think something wrong in my prior offered resource but I could not figure out what I was wrong. If you can figure out, please let me know.

Thanks,
Khuong

[gonzalogil26]

Hi @hoangkhuong272,

I think the problem comes in the establishment of a contract and its rules for an offered resources through the Swagger UI. Maybe because of a syntax issue.

Once the offered resource was created through the Swagger UI, I set the rules through the UI deployed at 8083 port and everything went fine.

Gonzalo

[sachinkumarUI]

Hi,
You can ask for the contract from the producer and update it with the rule and target:id links and send it for negotiation. Once the contract is agreed you should be able to access the artifactid created by the consumer using the agreementId link. Use it along with the remoteId agreement link to access the data.

One thing that I found strange was that the contract negotiation requires all the fields , even the one which haven't used while creating the contract

[CapacitorSet]

If anyone is stumbling across this from the IDS deployment examples, the solution I found was to update the Docker images for both the connector and the UI.