Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loki-canary can't use both authentication and x-scope-orgid (tenant-id) #5718

Closed
kovaxur opened this issue Mar 28, 2022 · 1 comment · Fixed by #5719
Closed

Loki-canary can't use both authentication and x-scope-orgid (tenant-id) #5718

kovaxur opened this issue Mar 28, 2022 · 1 comment · Fixed by #5719
Labels
stale A stale issue or PR that will automatically be closed.

Comments

@kovaxur
Copy link
Contributor

kovaxur commented Mar 28, 2022

Describe the bug
Loki-canary is unable to use both authentication and tenant-id settings at the same time.

To Reproduce

  1. Set username and password with the -user and -pass arguments
  2. Set tenant-id with the -tenant-id argument

Expected behavior
Users should be able to set both headers at the same time.

Environment:

  • Infrastructure: all
  • Deployment tool: all

Screenshots, Promtail config, or terminal output

if user != "" {
h = http.Header{"Authorization": {"Basic " + base64.StdEncoding.EncodeToString([]byte(user+":"+pass))}}
} else if tenantID != "" {
h = http.Header{"X-Scope-OrgID": {tenantID}}
}

@stale
Copy link

stale bot commented Apr 27, 2022

Hi! This issue has been automatically marked as stale because it has not had any
activity in the past 30 days.

We use a stalebot among other tools to help manage the state of issues in this project.
A stalebot can be very useful in closing issues in a number of cases; the most common
is closing issues or PRs where the original reporter has not responded.

Stalebots are also emotionless and cruel and can close issues which are still very relevant.

If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry.

We regularly sort for closed issues which have a stale label sorted by thumbs up.

We may also:

  • Mark issues as revivable if we think it's a valid issue but isn't something we are likely
    to prioritize in the future (the issue will still remain closed).
  • Add a keepalive label to silence the stalebot if the issue is very common/popular/important.

We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task,
our sincere apologies if you find yourself at the mercy of the stalebot.

@stale stale bot added the stale A stale issue or PR that will automatically be closed. label Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale A stale issue or PR that will automatically be closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant