TheHive-Project / TheHive-Project/Cortex
Cortex Responder Grouping seems not to work
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Request Type
Bug
Work Environment
| Question | Answer |
|---|---|
| OS version (server) | Debian |
| OS version (client) | 10 |
| Cortex version / git hash | 2.1.3-1 |
| TheHive Project 2016-2018, AGPL-V3 | |
| Package Type | Binary |
Problem Description
According to https://github.com/TheHive-Project/CortexDocs/blob/master/api/how-to-create-a-responder.md
baseConfig is used to group responder.
Name used to group configuration items common to several responders. This prevent the user to >enter the same API key for all responder flavors. The Cortex responder config page group >configuration items by their baseConfig.
For my understanding: I have 2 responders, and I don't need to configure for each the same API-Key as they are configured together.
I have 2 responders that have the same baseconfig, but they are not grouped.
Do I have a wrong understanding or is there something strange?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the responder configuration behavior described in the linked CortexDocs how-to-create-a-responder.md page and reproduce the report using two responders with the same baseConfig on Cortex 2.1.3-1. Check whether the configuration page groups their shared items as documented; done means confirming the expected behavior or identifying the specific mismatch to fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100