-
Notifications
You must be signed in to change notification settings - Fork 237
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
Version Upgrade of Analyzer makes all Analyzers invisible for TheHive (Cortex2) #75
Comments
Please make sure your TheHive uses a valid API Key |
I double checked, the key is correct, and it worked with exactly this key. |
Additional thing: |
+1 on this problem on Version 2.0.2 |
@csommerkapsch do you have homemade analyzers? |
@nadouani yes - a few. |
We found an issue where Thehive fails when reading analyzers that didn't define: license, author or url, can you double check that those metadata are set, until we fix this in TheHive? |
I checked this - all of my analyzers contain license, author and url in the .json File (I always copied that part over :) ) |
is it possible to call this API:
|
Yes with the API Key of the Analyzer User (ORG Admin doesn't have an API) and i get back all my analyzers with the full config. |
Do you see any analyzer with |
and |
I get some null entries in the curl command for analyzers i deleted because we dont use them. |
The issue is basically TheHive failing to either call Cortex API to fetch analyzers, or fails to parse what Cortex returns. The reasons that might make TheHive fails parsing the JSON returned by Cortex is that some required properties are Do you have any analyzer that has |
We have added a feature (Cortex 2.0.3 to be release in the next days) to allow you to list invalid analyzers and delete them. (#82) |
I re-downloaded only the .json files for the deleted analysers and now everything is working fine :) |
Welcome |
Request Type
Bug
Work Environment
Problem Description
After an update of an Analyzer, Cortex does not list anymore any Analyzer.
Reproduce
The text was updated successfully, but these errors were encountered: