Management API for Secrets

[bscholtes1A]

Feature Request

As discussed during committer group session, there is currently no management API enabling a participant to add/delete/update secrets from the Vault. In some cases, participant might have a direct access to the Vault itself to do the operations. But if an operator manages the connector for another entity (connector-as-a-service), then an API access is required for the participant to manage its secrets in self-service mode.

Which Areas Would Be Affected?

Management API of the Control Plane.

Why Is the Feature Desired?

In cases where a participant connector is managed by another entity (connector-as-a-service), then a management API for the secrets is required for the participant to be able to manage its secrets in self-service mode.

Solution Proposal

A SecretApi will be introduced which will be very similar to the other management APIs (assets, policy definitions...), with the exception that the secret API will not be included in the management API BOM.