User Interface for publishing/editing assets with the new DDO and the new SSI-based access control

[MBadea17]

Update the marketplace to allow publishing new assets or editing existing assets to accommodate the following:

• the new DDO structure, described here

• the description of the access credentials to asset or service (the "credentials" field), depending on whether SSI-based access control is activated (on) or deactivated (off):

  • for SSI off, access credentials are described as web3 addresses in either the allow or deny group, as documented here
  • for SSI on, access credentials are described as SSI verification policies, specific to walt.id implementation of the verifier component.

• signing the DDO structure (which is saved in the form of a JWS) with the appropriate private key, depending on whether SSI-based access control is on or off:

  • for SSI off, the DDO is signed with the web3 key of the publisher
  • for SSI on, the DDO is signed with one of the private keys of the Publisher, saved in its SSI wallet.

The flow to publish/edit an asset with SSI on:

• Publisher authenticates to its web3 wallet
• Publisher authenticates to its SSI wallet using the method described here
• Publisher edits the DDO fields
• Publisher is given the option to store additional descriptions of the asset
• Publisher calls the SSI wallet to list the private keys to sign the DDO
• Publisher selects the private key to sign the DDO
• Publisher calls the corresponding ocean.js function to sign the DDO
• Publisher calls the corresponding ocean.js function to save the DDO

The flow to publish/edit an asset with SSI off:

• Publisher authenticates to its web3 wallet
• Publisher edits the DDO fields
• Publisher is given the option to store additional descriptions of the asset
• Publisher calls the web3 method to sign the DDO
• Publisher selects the private key to sign the DDO
• Publisher calls the corresponding ocean.js function to sign the DDO
• Publisher calls the corresponding ocean.js function to save the DDO

[MBadea17]

When adding/editing an asset, the associated license can be provided by the user in two ways:

1. by uploading a file
   In this case, the marketplace should perform the following:

• save the file in IPFS using the default IPFS provider and retrieve the CID
• add the CID to the DDO
• continue the publishing process

2. by providing a link to where the license resides
   In this case, the marketplace should perform the following:

• add the provided link to the DDO
• continue the publishing process