What happened?
According to the documentation:
https://www.selenium.dev/documentation/grid/configuring_components/toml_options/
It's possible to protect the grid with basic auth like this:
[router]
username = "admin"
password = "myStrongPassword"
If it's not the way, how I can protect the grid?
Command used to start Selenium Grid with Docker
docker run -d --net grid -e SE_EVENT_BUS_HOST=selenium-hub \
-e SE_EVENT_BUS_PUBLISH_PORT=4442 \
-e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 \
-v ${PWD}/config.toml:/opt/bin/config.toml \
selenium/node-docker:4.1.0-20211123
No protection is there
Relevant log output
Operating System
MacOs BigSur
Docker Selenium version (tag)
latest
What happened?
According to the documentation:
https://www.selenium.dev/documentation/grid/configuring_components/toml_options/
It's possible to protect the grid with basic auth like this:
[router]
username = "admin"
password = "myStrongPassword"
If it's not the way, how I can protect the grid?
Command used to start Selenium Grid with Docker
docker run -d --net grid -e SE_EVENT_BUS_HOST=selenium-hub \ -e SE_EVENT_BUS_PUBLISH_PORT=4442 \ -e SE_EVENT_BUS_SUBSCRIBE_PORT=4443 \ -v ${PWD}/config.toml:/opt/bin/config.toml \ selenium/node-docker:4.1.0-20211123 No protection is thereRelevant log output
Operating System
MacOs BigSur
Docker Selenium version (tag)
latest