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

I send them with curl.

I set ClearML up with Kubernetes Helm.

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

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

The chart might be replacing that

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

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.

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

Oh, wait

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

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

yes, I send them manully.

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

<webserver>/api is a reverse proxy

What server are you using? a locally-installed server?

Just the apiserver

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

Or check the chart you're using 🙂

How can I fresh DB? Mongo or Redis?

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

More in detail?

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

where did you get it from?

Hi FloppyDeer99 ,
the users.get_all should be sent to the apiserver, not to the webserver. In any case, the header will not affect this request as the server will be using your user's identity (encoded in the authorization header) to resolve the company

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

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

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

No, I just restart the apiserver and webserver pod.

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