Also, the apiserver container log should also shed light on this matter as it lists all the configuration files it reads
I just checked if something changed in https://allegro.ai/clearml/docs/docs/deploying_clearml/clearml_server_config.html#web-login-authentication
so in your browser, do http://<server-address>:8008/login.supported_modes
Hi SuccessfulKoala55 , How can I now if I log in in this free access mode? I assume it is since in the login page I only see login field, not password field
This is what I get, when I am connected and when I am logged out (by clearing cache/cookies)
Hi JitteryCoyote63 ,
The logout issue has been reported and will be patched and released as v1.0.1 in the next few days.
As for the static accounts support, this was actually tested and is working for me - can you provide more info? Sometimes, this might indicate the WebUI fails to connect to the API server and (incorretcly) assumed it's in the "free access" mode, but when you try to actually log in with some user name you'll get an error - can you actually log in in this free access mode?
The access mode is actually not related to the cookies themselves (wouldn't be much of a secure mode if it was), but depends on server configuration
How do you configure the server? Did you use an apiserver.conf file with the fixed users passwords?
Well, basic.enabled: false means the server is indeed not configured for user/password access... 😞
I added the pass_hashed and restarted the server, still get the same problem
under /opt/clearml/config/apiserver.conf
Should work now as well - wanna share your docker-compose.yml ?
Thanks for the help SuccessfulKoala55 , the problem was solved by updating the docker-compose file to the latest version in the repo: https://github.com/allegroai/clearml-server/blob/master/docker/docker-compose.yml
Make sure to do docker-compose down & docker-compose up -d afterwards, and not docker-compose restart
The only thing that changed is the new auth.fixed_users.pass_hashed field, that I don’t have in my config file
The easiest was is to call the server's /login.supported_modes endpooint