Add MIMIR_AUTH_TOKEN for self-hosted Mimir #505
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For self-hosted Mimir installations, an authenticating reverse proxy is typically required (https://grafana.com/docs/mimir/latest/manage/secure/authentication-and-authorization/#with-an-authenticating-reverse-proxy).
Implementations can choose any method to perform that authentication, but it's typically basic auth (which is already supported here), or a Bearer token in the Authorization header. This adds support for the latter.