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

Error incorrect filter keys not existing in any schema definition when running background task with specific filters #5315

Closed
SouadHadjiat opened this issue Dec 28, 2023 · 0 comments
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP filters temporarily used to identify filter issue to facilitate filter team’s work identification solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@SouadHadjiat
Copy link
Member

Description

When creating a background task with some specific filters (reproduced with source entity on relationships), I have this error :
incorrect filter keys not existing in any schema definition

Capture d'écran 2023-12-27 175809

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: 5.12.14
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

I reproduced locally with "source entity" filter, but I suspect if can be reproduced with other filters (target entity, source and target types)

  1. Go to Data -> Relationships
  2. Filter by source entity
  3. Try to create a background task (remove or add a label for example) => it fails with the above error

Additional information

I suspect buildQueryFiltersContent function which doesn't test correctly "key" (it's an array, not a string)

@SouadHadjiat SouadHadjiat added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Dec 28, 2023
@Archidoit Archidoit added the filters temporarily used to identify filter issue to facilitate filter team’s work identification label Dec 29, 2023
@Archidoit Archidoit self-assigned this Dec 29, 2023
Archidoit added a commit that referenced this issue Jan 3, 2024
Archidoit added a commit that referenced this issue Jan 4, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 4, 2024
@SamuelHassine SamuelHassine added this to the Release 5.12.16 milestone Jan 8, 2024
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 critical use to identify critical bug to fix ASAP filters temporarily used to identify filter issue to facilitate filter team’s work identification solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

3 participants