browser.json prevents user credentionals to be checked and specific user browsers list

[benzman81]

I installed moon using the helm chart. A default quota with browsers.json is created. Now, if I add a foo.json then I would expect, that if I use the url like http://foo:foo-password@mynode:31306/wd/hub, the user foo will be validated with his password and its browsers list from foo.json will be used. The current behavior always uses the browsers.json and does not validate the correct password. Only if I set the browsers.json to empty or remove it completly the user data is respected. Is this works as designed or is this a bug/missconfiguration?

[vania-pooh]

Related to https://github.com/aerokube/ggr/issues/254. This is a particularity in some Selenium client libraries that do not send Authorization header before receiving 401 error. If we always send 401, then guest quota will not work. So we don't send 401 by default you this is why this happens.