Workflow for the creation of shared resources using encrypted metadata

API & Customization issues
1

Hi all,

After the beta of encrypted metadata I want to update our API-integrations to also use the new resource-types.

Currently I have successfully implemented the following features in our integrations:

  • APIv4 - read own and shared resources
  • APIv4 - create own and shared resources
  • APIv5 - read own and shared resources, including encrypted metadata

For the APIv4 I have seen enough documentation for the creation and sharing of the resources; e.g. https://www.passbolt.com/docs/development/resources/sharing/

For reading APIv5 resources I used the workflow from: https://www.passbolt.com/blog/the-road-to-passbolt-v5-encrypted-metadata-and-other-core-security-changes-2

However I have not seen workflow how to create and correctly share an APIv5 resource. Are there any resources, or can someone help me in the right direction?

Regards,

2

As @dion and I were discussing in a support ticket: The goal is for there to be a passbolt SDK guideline so that whichever tooling is created follows best-practice and the SDK developers are the only folks working with the API. Currently the go-cli is the only tool that’s under development by the community (although it’s hosted under the passbolt github account).

I have been learning about working with the passbolt api for handling metadata encryption and I offer that repo here for purely informational purposes.

https://github.com/gyaresu/passbolt-api-tools

Gareth

1 Like