feature: Ecrypted Submission Responses

[bryan-robitaille]

Summary | Résumé

Main Features:

• Encrypts a response with aes-256-gcm by getting the Public key from the Web App database and returns the encrypted values. The public key is cached for a 5 minute period to reduce the calls required to the database.
• Utility script under /utils that demonstrates how to request an access token by using the private key and the resulting access token to retrieve a particular response. Once we have the /new endpoint finalized we can modify the script to not ask for the response Name to retrieve.
• Extends Express Request type so that the Authentication middleware can add the serviceAccountId on the request for downstream controllers to use.
• Adds a singleton database connector that creates a connection to the web app database that can be reused.

Medium sized Additions to project:

• Swapped from compiling to CommonJs to ES Modules. This means that we can use all the latest ECMA goodies with the only big trade off being we need to add the .js extention of all of our relative module imports.

Small Additions to project:

• logMessage() is now available like the web app from @lib/logger.js
• Default debugger profile that connects to running task in a terminal
• Removed Nodemon and using the built in watch functionality of tsx.

Test instructions | Instructions pour tester la modification

Create some responses in the vault and retrieve them using pnpm retrieve from the utils folder.

[patheard]

Minor comment but what would you think of moving the utilTokenGeneration.mjs script into the utils folder.

[bryan-robitaille]

Minor comment but what would you think of moving the utilTokenGeneration.mjs script into the utils folder.

I was going to remove it completely later on since the same functionality can now be achieved through the responseRetriever function.

[bryan-robitaille]

@patheard the code base is also going to go through a refactor where the utils folder will probably become examples with multiple coding languages.

[craigzour]

Nice work :)

There are probably a lot of comments that you may want to ignore either because I missed the point or because you just want to tackle those during our first refactoring session.

[patheard]

Looks good on my end - nicely done on this!

[craigzour]

LGTM! Good job :)