From 93dcc89ac9796e3e7770e37ad603a49071ce53c0 Mon Sep 17 00:00:00 2001 From: Jason Sherman Date: Mon, 24 Jun 2024 10:43:21 -0700 Subject: [PATCH] remove encrypted db not from docs. Signed-off-by: Jason Sherman --- docs/chefs-external-api-configuration.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/chefs-external-api-configuration.md b/docs/chefs-external-api-configuration.md index 469238e24..12c421214 100644 --- a/docs/chefs-external-api-configuration.md +++ b/docs/chefs-external-api-configuration.md @@ -8,8 +8,6 @@ The solution documented here allows a Form Designer to specify an External API o To achieve this, Form Designers will configure their External API, get approval from CHEFS and configure their form components to call a CHEFS proxy that forwards the call to the External API. -Any private data required in the configuration (i.e. API Key) will be stored as encrypted data in the CHEFS database. It will not be a part of the form schema. - This External API is associated with a single form, but as other hierarchies are introduced in CHEFS (form bundles, tenants, etc), we can associate them with those items and prevent redundancy. ## External API Configuration