Basic Auth - Doc could add some clarity
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 717
- Forks
- 1.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 19
Description
The article https://prometheus.io/docs/guides/basic-auth/ describes basic auth well and we have set it up in a way that requires username/password for the prometheus web interface running on a public server. However, when trying to scrape the prometheus data from localhost, the same basic auth seems to be applied.
It is not clear from the docs whether it is possible to only apply basic auth to a specific interface and disable it for "localhost" to avoid having to specify the same creds for the scrape config as we currently apply via a secret in Kuberentes.
If this is not possible, it would be nice to clarify this in the docs, e.g. "If you enable basic auth at all, all users on the web interface and prometheus will require credentials to access the system, it is not possible to disable auth for specific interfaces"
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 with the basic-auth guide at https://prometheus.io/docs/guides/basic-auth/ and verify whether authentication can be limited to the public web interface while allowing localhost scrapes without credentials. Done means the guide clearly states the supported behavior and explains the required scrape configuration or the limitation if localhost cannot be exempted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100