-
Notifications
You must be signed in to change notification settings - Fork 761
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
No instructions on how to work with GRR installed using Docker Compose #1092
Comments
Hello bogdan77604, thank you for opening this issue. To enable the authentication prompt in the UI you can update the server configuration file by adding To add another user, that can then be used in the authentication you would connect to e.g. the grr-admin-ui container and add the user:
( The docker compose stack has a I hope this helps, let us know if you have further questions! |
Hi @bogdan77604 |
Hi, @victorle-sec |
@bogdan77604 we would appreciate if you could share a bit more information and the logs, so that we could look into the problem:
Do you mean Fleetspeak server? Does it happen when you turn up the docker compose? Could you please share the logs?
Please describe what exactly you were trying to do so that we could try to reproduce the issue. Also, if you have any log files, we would appreciate them as well. |
Environment
Describe the issue
I installed GRR using the docker composer from the official gitHub.
I pulled it up and then went to the GUI. I was not prompted for authentication, but was automatically logged in as gui_user. Moreover, to enter the database settings, I had to search for the .env file to find the default authorisation data.
I wanted to run the command "grr_config_updater show_user", but I tried to enter different containers and none of them executed without an error
I also don't have clients installed properly...
Could someone please explain how to work with this utility in the docker compose
Error logs
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: