You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We build the quickwit cluster and grafana UI. Grafana side is calling quickwit API, through quickwit datasource.
Currently, anyone can call the quickwit search API or the APIs in the quickwit swagger of control plane if he knows the URL. This is not what we want.
We want add some auth in quickwit side, and grafana side will call the quickwit side with related credentials. Or it can be in another way, grafana and quickwit side can do certificate mutual authentication.
Any way, we want quickwit not expose its API directly and want to do some protection.
So want to query and confirm if quickwit side support adding some auth currently?
Thanks a lot.
The text was updated successfully, but these errors were encountered:
@rdettai any pointers to how this proxy can be setup? In the context of cluster-mode when qw nodes need to talk to each other, it seem the proxy with auth is a problem for that.
We build the quickwit cluster and grafana UI. Grafana side is calling quickwit API, through quickwit datasource.
Currently, anyone can call the quickwit search API or the APIs in the quickwit swagger of control plane if he knows the URL. This is not what we want.
We want add some auth in quickwit side, and grafana side will call the quickwit side with related credentials. Or it can be in another way, grafana and quickwit side can do certificate mutual authentication.
Any way, we want quickwit not expose its API directly and want to do some protection.
So want to query and confirm if quickwit side support adding some auth currently?
Thanks a lot.
The text was updated successfully, but these errors were encountered: