You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Ocean Enteprise, the DDO of an asset comes in the form of a Verifiable Credential, which is signed with the private key of the publisher and saved as a JWS. Depending on the configuration, it can be signed either internally or by an external API.
As-is situation
Currently, when publishing an Ocean Enterprise asset (DDO version v.5.0.0) that needs to be signed, there is no standardized process. Each component (CLI, marketplace, or others) handles this separately, leading to inconsistencies and duplicated effort.
Proposal:
Add a common solution to the Ocean library that allows all components to leverage shared functionality for signing DDOs. This will ensure consistency, reduce redundancy, and streamline the process for all users and components.
The text was updated successfully, but these errors were encountered:
Context:
In Ocean Enteprise, the DDO of an asset comes in the form of a Verifiable Credential, which is signed with the private key of the publisher and saved as a JWS. Depending on the configuration, it can be signed either internally or by an external API.
As-is situation
Currently, when publishing an Ocean Enterprise asset (DDO version v.5.0.0) that needs to be signed, there is no standardized process. Each component (CLI, marketplace, or others) handles this separately, leading to inconsistencies and duplicated effort.
Proposal:
Add a common solution to the Ocean library that allows all components to leverage shared functionality for signing DDOs. This will ensure consistency, reduce redundancy, and streamline the process for all users and components.
The text was updated successfully, but these errors were encountered: