Skip to content

Commit

Permalink
Merge pull request #44 from usingtechnology/fix/event-stream-service
Browse files Browse the repository at this point in the history
url error in document
  • Loading branch information
usingtechnology authored Jul 10, 2024
2 parents 7960126 + d491c80 commit dc5cd88
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion docs/Capabilities/Integrations/Event-Stream-Service.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,8 @@ An example to show the overall structure of an event message is:
To securely facilitate transmission of sensitive data between systems, CHEFS will encrypt the payloads for `PRIVATE.forms` events.

Initially, CHEFS will encrypt the payload using an `aes-256-gcm` that requires a `sha256` hash as a key (256 bits/32 bytes/64 characters).
CHEFS will use the (cryptr)[https://github.com/MauriceButler/cryptr] JavaScript library. External applications are not required to use Node.js/JavaScript but will have to test their own implmentation or library.

CHEFS will use the [cryptr](https://github.com/MauriceButler/cryptr) JavaScript library. External applications are not required to use Node.js/JavaScript but will have to test their own implmentation or library.

The Form Designer will have to `enable` private messages and encryption. CHEFS can generate a key or the Form Designer can provide the key. In either case, only CHEFS and the Form Designer should know the key. The Form Designer should store the key securely and make it accessible to their application/service/system following best practices.

Expand Down

0 comments on commit dc5cd88

Please sign in to comment.