quickwit-oss / quickwit-oss/quickwit
does quickwit support any auth to protect the quickwit APIs?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the Quickwit search API and control-plane Swagger entry points for any existing authentication or mutual-TLS support, then review how the Grafana datasource calls them. Done means confirming a supported protection mechanism or defining the implementation scope needed to secure those API calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100