It’s probably unrelated 😬 I’ll keep you posted.
Well, it should appear (if you cleared all cookies)
Ok I think I might have found the problem.
ah ok. So only solution is changing the hardcoded one…
I will be looking into docs to find the right env variable. If you know it I’d appreciate you telling me 😄 SuccessfulKoala55
btw - if you didn't login, the UI probably used a previous token. changing the session secret might have messed that up 🙂
No it doesn’t work from entirely new browser too. 😞
As this is a staging instance. let me remove and deploy without these changes.
Is this after doing a user login in the UI?
yep it was unrelated.. sorry
Thanks for your help
CLEARML__SECURE__HTTP__SESSION_SECRET__APISERVER
No, this is unrelated
CLEARML__SECURE__HTTP__SESSION_SECRET__APISERVER
Does this one need to be changed?
Awesome info! Thanks!
What env variable should I use?
Also maybe I can block unauthenticated access to that endpoint too, I guess clearml-agent doesn’t use it!
I’m using cloud-ready helm chart (with some modifications)
So for api-server deployment:
no. apparently changing these variables causes something to fail.
Well, actually it's used by both ClearML SDK and agent since both start with credentials but generate a token as soon as possible (more secure and faster)
Oh, sorry! both user_key and user_secret are with a single underscore :)
The login prompt doesn’t appear (I tried removing cookies and all too)
Can you show exactly what you changed in the docker compose?
SuccessfulKoala55 I’m getting 405 on api calls with the configuration you proposed. (btw I think USER_KEY is right, with a single underscore)
are you sure you're using the latest docker images?
I might be wrong about the company_id 🙂 - but in case I'm wrong, you'll see it quickly since you won't be able to login with new users to the UI 🙂
Oh well it doesn’t work for me then… I keep getting errors.