Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sign Verifiable Credential #1878

Open
AdriGeorge opened this issue Nov 21, 2024 · 0 comments · May be fixed by #1877
Open

Sign Verifiable Credential #1878

AdriGeorge opened this issue Nov 21, 2024 · 0 comments · May be fixed by #1877
Labels
Enterprise Type: Enhancement New feature or request

Comments

@AdriGeorge
Copy link
Collaborator

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.

@AdriGeorge AdriGeorge added the Type: Enhancement New feature or request label Nov 21, 2024
@AdriGeorge AdriGeorge linked a pull request Nov 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enterprise Type: Enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants