You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The enrichment connector does not utilize the API URL from the config file, resulting in the connector not working.
Environment
OS (where OpenCTI server runs): Ubuntu 24.04 LTS
OpenCTI version: 6.2.5
OpenCTI client: Python (probably)
Other environment details: N/A
Reproducible Steps
Steps to create the smallest reproducible scenario:
Enter domain/IP in the docker-compose.yml
Attempt to perform analysis via enrichment in the OpenCTI front end
Expected Output
Artifact is sent to Cape for analysis
Actual Output
Connector throws multiple errors which shows the URL not being pass, and the handling of that error results in a type error.
Additional information
In the file cape-sandbox,py in the container, entering the address of cape on line 47 fixes the issue.
Screenshots (optional)
The text was updated successfully, but these errors were encountered:
human4357
added
bug
use for describing something not working as expected
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jul 16, 2024
Description
The enrichment connector does not utilize the API URL from the config file, resulting in the connector not working.
Environment
Reproducible Steps
Steps to create the smallest reproducible scenario:
Expected Output
Artifact is sent to Cape for analysis
Actual Output
Connector throws multiple errors which shows the URL not being pass, and the handling of that error results in a type error.
Additional information
In the file
cape-sandbox,py
in the container, entering the address of cape on line 47 fixes the issue.Screenshots (optional)
The text was updated successfully, but these errors were encountered: