Or check the chart you're using 🙂

Also - did you start with a fresh DB after changing the default company value?

Are you sending these requests manually?
COK. In any case, you should be looking at the

I send them with curl.

Well, for some reason the webserver auth user entry is probably created using the incorrect company_id - the best thing to do it exec into the mongo container and check the actual company value assigned to the webserver user

<webserver>/api is a reverse proxy

OK, so the company you're referring to is encoded in the authorization header

But you’re not using the webserver, you’re sending the cURL requests manually, aren’t you?

yes, I send them manully.

In any case the user associated with the credentials you use is not assigned to the same cinoany ID you replaced

More in detail?

Just the apiserver

where did you get it from?

Is this the cloud-ready version? or the legacy chart?

I set ClearML up with Kubernetes Helm.

These values are overridden in the k8s deployment. See https://github.com/allegroai/clearml-server-k8s/blob/master/clearml-server-cloud-ready/templates/secrets.yaml

Thanks a lot! I’ ll replace credentials with new user in assigned to a new company ID to call users.get_all again.

The chart might be replacing that

In any case, the said credentials are valid for the company ID defined using 

apiserver.default_company

It really works for apiserver, but webserver does not have the default_company configuration.

Are you sending these requests manually?
OK. In any case, you should be looking at the

But you're not using the webserver, you're sending the cURL requests manually, aren't you?

I have another question. Does the following apis in the picture are served by both of apiserver and webserver, or just one of them ?

Also - did you start with a fresh DB after changing the default company value?

No, I just restart the apiserver and webserver pod.

A users.get_all request will return the users in the company to which the calling user is authenticated to. So, if you only get the users from the original default company ID and not those from newID, it means the credentials you're using to call this endpoint are associated in the server with the original company ID, and not with the newID

the webserver secret isn't there

In any case, the said credentials are valid for the company ID defined using apiserver.default_company

Oh, wait

I set it up with the following documentation: https://allegro.ai/clearml/docs/docs/deploying_clearml/clearml_server_kubernetes_helm.html