N-Times Usage Policy is not properly implemented

[ip312]

When trying to use the N-Time policy I got an error message. Versions: DSC - 8.0.1; MDS Frontend - 10.0.1.

Steps to reproduce: Select N Times Usage as policy Number ≤ 5 Contract validity period: from 2022-09-01 to 2022-09-30

The error message (Frontend):
Error on POST /api/ids/resource/update {"status":417,"statusText":"","headers":{"x-content-type-options":"nosniff","x-xss-protection":"1; mode=block","cache-control":"no-cache, no-store, max-age=0, must-revalidate","pragma":"no-cache","expires":"0","strict-transport-security":"max-age=31536000 ; includeSubDomains","x-frame-options":"DENY","content-type":"application/json","transfer-encoding":"chunked","date":"Wed, 07 Sep 2022 14:50:46 GMT","connection":"close"},"config":null,"request":null,"data":{"details":{"reason":{"properties":null,"@id":"https://w3id.org/idsa/code/MALFORMED_MESSAGE"},"payload":"The message could not be parsed due to an error in the message. Note that, due to being unable to parse this message, the ID of the correlating message is incorrect. Error: The following mandatory field(s) of Constraint are not filled or invalid: ids:pipEndpoint. Note that the value of \"@id\" fields MUST be a valid URI (e.g. emails preceded by \"mailto:\"). Mandatory fields are: leftOperand, operator, pipEndpoint","type":"de.fraunhofer.iais.eis.RejectionMessageImpl"},"message":"Received unexpected response message."}}

The error message (Connector):
DEBUG - Received unexpected response message. [response=({reason=https://w3id.org/idsa/code/MALFORMED_MESSAGE, payload=The message could not be parsed due to an error in the message. Note that, due to being unable to parse this message, the ID of the correlating message is incorrect. Error: The following mandatory field(s) of Constraint are not filled or invalid: ids:pipEndpoint. Note that the value of "@id" fields MUST be a valid URI (e.g. emails preceded by "mailto:"). Mandatory fields are: leftOperand, operator, pipEndpoint, type=class de.fraunhofer.iais.eis.RejectionMessageImpl})]

[ip312]

It has been found that the problem is on the broker side. Closed.