Price: 0
Number of applications: 3
27.03.26 (inclusive)
Contractual
Idea
ICT tasks
Media sphere
Neurotechnology and artificial Intelligence
Software/ IS
The existing Custom Integration supports URL/method/payload/headers, but substitutions currently only work in payload. According to the requirements, the secrets must be kept separate from the main integration configuration; stored in encrypted form; be available by name for substitutions and calculations; have a privacy flag.
A custom_integration_secrets table has been created in the database with the specified fields, indexes, and uniqueness (custom_integration_id, name). The computed_fields (JSON) field with the default [] has been added to custom_integrations. A secret can be created/updated/deleted via the API. Under no circumstances does the real secret value appear in the API and logs (only the mask/is_set). When trying to create a secret with the same name within the same integration , an understandable validation error is returned.
Dmitry Pavlovsky
Purpose and description of task (project)
Add the basic ability to store secrets (in encrypted form) to the Custom Integration Request and prepare a data schema for calculated fields in order to further use this in substitutions {{secret.*}} / {{calculated.*}} and in JS computing
Whatsapp
