From c71af8f8a9986e365a21dcaaeb337e38edc12623 Mon Sep 17 00:00:00 2001 From: mmattel Date: Mon, 19 Aug 2024 10:10:37 +0200 Subject: [PATCH] [docs-only] Document the expected location of the ocmproviders.json file --- services/ocm/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/ocm/README.md b/services/ocm/README.md index 0b28234e2c..2794d382f3 100644 --- a/services/ocm/README.md +++ b/services/ocm/README.md @@ -17,7 +17,7 @@ Internal GRPC APIs: The `ocm` services implements an invitation workflow which needs to be followed before creating federated shares. Invitations are limited to trusted instances, however. -The list of trusted instances is managed by the `ocmproviderauthorizer` service. The only supported backend currently is `json` which stores the list in a json file on disk. +The list of trusted instances is managed by the `ocmproviderauthorizer` service. The only supported backend currently is `json` which stores the list in a json file on disk. Note that the `ocmproviders.json` file, which holds that configuration, is expected to be located in the root of the ocis config directory. Example `ocmproviders.json` file: ```