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

Insufficient Rights To Perform This Action #87

Closed
hackdefendr opened this issue Apr 10, 2018 · 8 comments
Closed

Insufficient Rights To Perform This Action #87

hackdefendr opened this issue Apr 10, 2018 · 8 comments
Labels

Comments

@hackdefendr
Copy link

hackdefendr commented Apr 10, 2018

Insufficient Rights To Perform This Action

Request Type

Bug or Issue

Work Environment

Question Answer
OS version (server) Ubuntu
OS version (client) Ubuntu
Cortex version / git hash Current
Package Type Binary
Browser type & version Chrome

Problem Description

When I click on the Cortex logo to go back to the main analyzers page, I receive a little red pop up that reads Insufficient Rights To Perform Action

Steps to Reproduce

  1. Follow the instructions for installation
  2. Follow the steps for configuration
  3. Try to access the main Cortex analyzers page
  4. I really don't know

Possible Solutions

I tried giving ownership of my Cortex-Analyzer folder to the user cortex, but this had no effect. I am stuck and do not know what else to look for.

Complementary information

2018-04-10 13:21:32,454 [INFO] from org.thp.cortex.services.ErrorHandler in application-akka.actor.default-dispatcher-172 - GET /api/analyzer?rang
e=all returned 403
org.elastic4play.AuthorizationError: Insufficient rights to perform this action
        at org.elastic4play.controllers.Authenticated$$anon$1.$anonfun$invokeBlock$1(Authenticated.scala:240)
        at scala.concurrent.Future.$anonfun$flatMap$1(Future.scala:304)
        at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:37)
        at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)
        at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
        at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:91)
        at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)
        at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:81)
        at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:91)
        at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:40)
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:43)
        at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
        at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
        at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
@3c7
Copy link

3c7 commented Apr 10, 2018

The errormessage refers to the web ui directly and should have nothing to do with the analyzers directory. If you reload the whole page, are you still logged in? Are you logged in as a superadmin or as an orgadmin?

@hackdefendr
Copy link
Author

I've logged out and logged in, refreshed the page, cleared the browser cache. Nothing seems to work.

@3c7
Copy link

3c7 commented Apr 10, 2018

Okay, have you created another Organisation? The members of the cortex org are (as superadmins) not able to use analyzers.

@hackdefendr
Copy link
Author

Well no I had not, because that step was not documented anyplace that I could find.

This did resolve my issue though. Thanks.

@nadouani
Copy link
Contributor

nadouani commented Apr 10, 2018

Hello @hackdefendr, I’m sorry but if you have followed the steps of the Quick start guide, you could have found your issue.

https://github.com/TheHive-Project/CortexDocs/blob/master/admin/quick-start.md

That said, clicking on the logo should redirect to the right page, which is not correcly working here.

@hackdefendr
Copy link
Author

hackdefendr commented Apr 10, 2018 via email

@3c7
Copy link

3c7 commented Apr 11, 2018

We're aware that our documentation needs some polish. At the bottom of the deb installation guide the configuration guide is linked which mentions the different types of user accounts, also. But doesn't matter, good it works for you now.

@To-om To-om added the doc label Apr 13, 2018
@kmahyyg
Copy link

kmahyyg commented Apr 8, 2024

Same issue here... Using "run with docker" guide from thehive, not mention this problem...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants