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

MISP Analyzer only queries first configured MISP instance #378

Closed
ParanoidRat opened this issue Nov 20, 2018 · 1 comment
Closed

MISP Analyzer only queries first configured MISP instance #378

ParanoidRat opened this issue Nov 20, 2018 · 1 comment
Labels
category:bug Issue is related to a bug scope:analyzer Issue is analyzer related

Comments

@ParanoidRat
Copy link

Request Type

Bug

Work Environment

Question Answer
OS version (server) Docker Swarm service
OS version (client) N/A
Cortex Analyzer Name MISP
Cortex Analyzer Version 2.0
Cortex Version 2.1.2
Browser type & version N/A

Description

I have two MISP instances configured with two values for name, url, key, cert_path (both pointing just to /etc/ssl/certs) and disabled server cert verification (cert_check: false).

When analyzer is invoked it returns results (including empty results for non-existent items) only from one instance. No errors in logs.

Steps to Reproduce

  1. Deploy Cortex as a service on Docker Swarm
  2. Configure MISP analyzer with two MISP instances as described above
  3. Search for something that does or does not exist in both (or one) instances
@3c7 3c7 added category:bug Issue is related to a bug scope:analyzer Issue is analyzer related labels Jan 22, 2019
@3c7
Copy link
Contributor

3c7 commented Jan 22, 2019

Hey @ParanoidRat, I cannot reproduce the bug. If you want to use different MISP servers with regular trusted certificates, just leave the cert_path empty.
Analyzer configuration should be like that:
screenshot from 2019-01-22 08-30-53
Closing this issue for now.

@3c7 3c7 closed this as completed Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bug Issue is related to a bug scope:analyzer Issue is analyzer related
Projects
None yet
Development

No branches or pull requests

2 participants