Skip to content

Latest commit

 

History

History
18 lines (10 loc) · 1.45 KB

contract-negotiation.md

File metadata and controls

18 lines (10 loc) · 1.45 KB

Contract Negotiation - simple flow

Usage Control is disabled by default. If you want to enable it (mandatory for contract negotiation), please check "Enabling usage control".

If mandatory, for other connectors, you can perform contract negotiation with other connector (not TRUE Connector) or with TRUE Connector. There is default contract offer that will be sent if ContractRequestMessage is received. It will allow consuming of resource.

Assuming you are running docker instance on local machine. If not, please update hostname to match your scenario.

You can use provided Postman collection and Postman environment; import both files into Postman and perform Contract Negotiation automatically or do this step by step, as described below.

As can bee seen in screenshot, there is 3 Contract Negotiation flows:

  • Contract Negotiation - flow with default ContractRequest message
  • Contract Negotiation (Role/Purpose) - flow with updating default Contract policy, to include Role permission, in order to demonstrate interaction with PIP, necessary for checking Roles or Purpose policies
  • Contract Negotiation WS - flow with default ContractRequest message in WS (WebSocket) communication

TRUE Connector Postman