Open leetn00b opened 1 year ago
Hello @leetn00b,
Thanks. This issue is linked to #2585.
A raw JSON parameter field seems to be a little wide. Can you please describe a little more your use case so we can understand better which can of parameters you actually need?
Thanks a lot.
Kind regards, Samuel
Hi @SamuelHassine,
I have seen several use cases for raw json to be accepted while developing connectors, for example, the Export Report PDF connector could utilize several values from a JSON for formatting reports. The other use case is that I wanted to develop a connector for decompressing zip archives that use custom passwords, thus requiring input from the user to specify the password for decompressing.
FYI this is YungBinary, I just use this as a secondary account for another environment.
Use case
We are looking for a solution where we can send JSON data to custom Internal Enrichment Connectors. Right now no custom data can be sent when enriching an observable.
Proposed Solution
Use a field for inputting data that can be ingested by enrichment connectors per enrichment.