This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit 19aefbbf46351b677c97018940d7636c55405b72 Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Apr 15 14:24:05 2022 +0200 Google Secret Manager: added notes about permissions needed to use the feature at service account level --- docs/user-manual/modules/ROOT/pages/security.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/user-manual/modules/ROOT/pages/security.adoc b/docs/user-manual/modules/ROOT/pages/security.adoc index b681da76846..5168f77eecb 100644 --- a/docs/user-manual/modules/ROOT/pages/security.adoc +++ b/docs/user-manual/modules/ROOT/pages/security.adoc @@ -270,7 +270,9 @@ In this case if the secret doesn't exist or the secret exists, but the username NOTE: For the moment we are not considering the rotation function, if any will be applied, but it is in the work to be done. -The only requirement is adding `camel-google-secret-manager` JAR to your Camel application. +There are only two requirements: +- Adding `camel-google-secret-manager` JAR to your Camel application. +- Give the service account used permissions to do operation at secret management level (for example accessing the secret payload, or being admin of secret manager service) ==== Using Azure Key Vault
