Skip to content

Commit

Permalink
remove encrypted db not from docs.
Browse files Browse the repository at this point in the history
Signed-off-by: Jason Sherman <[email protected]>
  • Loading branch information
usingtechnology committed Jun 24, 2024
1 parent f61fe4c commit 93dcc89
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions docs/chefs-external-api-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 93dcc89

Please sign in to comment.