TheHive-Project / TheHive-Project/Cortex
Unable to link TheHive 4 and Cortex 3
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Unable to link TheHive 4 and Cortex 3
Request Type
Bug
Work Environment
| Question | Answer |
|---|---|
| OS version (server) | Debian 10 |
| OS version (client) | Windows 10 |
| Cortex version / git hash | 3.0.1-1 |
| Package Type | DEB |
| Browser type & version | Chrome |
Problem Description
It is impossible to link TheHive 4 and Cortex 3.
Steps to Reproduce
The Hive 4 and Cortex 3 work very well independently.
The ticket management in TheHive is perfect, I was able to import the templates etc..
Cortex works very well, I was able to test with VirusTotal.
But that's where my problem comes in, I can't link TheHive4 and Cortex3. I did create a user with "read and analyse" rights in Cortex, then generated an API Key that I indicated in the "application.conf" file of TheHive by mentioning the URL of my Cortex, which is the same VM.
I searched everywhere to find a solution, modify both sides of the configuration files but nothing to do, the link was not created.
Complementary information
For TheHive part:
Scalligraph0.1.0-SNAPSHOT
TheHive4.0.0-1
Play2.8.2
For Cortex part:
Cortex3.0.1-1
Elastic4Play1.11.5
Play2.6.23
Elastic4s6.5.1
ElasticSearch client6.5.2
And my TheHive4 application.conf file:

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 reported TheHive application.conf URL and API-key settings, then reproduce the link attempt using TheHive 4.0.0-1 and Cortex 3.0.1-1 on the listed environment. Done means TheHive successfully links to Cortex using the configured connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100