Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tenable-vuln-management] Fails to start with KeyError: 'connector' #3518

Open
gileri opened this issue Feb 27, 2025 · 0 comments · May be fixed by #3541
Open

[tenable-vuln-management] Fails to start with KeyError: 'connector' #3518

gileri opened this issue Feb 27, 2025 · 0 comments · May be fixed by #3541
Assignees
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran.
Milestone

Comments

@gileri
Copy link
Member

gileri commented Feb 27, 2025

Description

Fails to start with KeyError: 'connector'

Environment

  1. OS (where OpenCTI server runs): Official container image
  2. OpenCTI version: OpenCTI 3
  3. OpenCTI client: { e.g. frontend or python }
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Run the connector
  2. Get error

Expected Output

No error

Actual Output

Traceback (most recent call last):
  File "/opt/opencti-connector-tenable-vuln-management/main.py", line 16, in <module>
    connector = Connector()
                ^^^^^^^^^^^
  File "/opt/opencti-connector-tenable-vuln-management/tenable_vuln_management/connector.py", line 59, in __init__
    self.config = ConfigConnector()
                  ^^^^^^^^^^^^^^^^^
  File "/opt/opencti-connector-tenable-vuln-management/tenable_vuln_management/config_variables.py", line 17, in __init__
    self.load["connector"]["type"] = "EXTERNAL_IMPORT"
    ~~~~~~~~~^^^^^^^^^^^^^
KeyError: 'connector'

Additional information

Screenshots (optional)

@gileri gileri added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 27, 2025
@flavienSindou flavienSindou self-assigned this Mar 3, 2025
@flavienSindou flavienSindou added filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 3, 2025
@flavienSindou flavienSindou added this to the Bugs backlog milestone Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran.
Projects
None yet
2 participants