SuccessfulKoala55 I found the issue thanks to you: I changed a bit the domain but didn’t update the apiserver.auth.cookies.domain
setting - I did it, restarted and now it works 🙂 Thanks!
Did you set it somewhere? This is usually done in the apiserver.auth.cookis.domain
setting
Yes, I set:auth { cookies { httponly: true secure: true domain: ".clearml.xyz.com" max_age: 99999999999 } }
It always worked for me this way
Can you show me the browser's network tab when you try to login?
Hi JitteryCoyote63 ,
This initial error will be there most of the times since the WebApp tries to access, gets an error, and than gets redirected to the login. The question is why the login page doesn't work
See the Set-Cookie
header, it specifies Domain: .clearml.
, which probably causes the browser to ignore the cookie and not set it in the session
The console errors are inconsequential
However, the server returns auth.login
with 200
, so the question is why isn't the token generated by that response stored in the browser
Can you show the response for the auth.login call and the request and headers for the following calls?
Can I see the response headers from the auth.login
call? Specifically, the set cookie header - I suspect the cookie might be domain-specific and thus not stored by the browser (since I can't see it used in the following requests)