chore: ensure internalQuerier utilizes identical authMiddleware to API #3439
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.
What this PR does:
This PR ensures the authentication middleware used by the internalQuerier is the same that is used by the API struct. I was worried this might be causing an issue with queries for single binary users with
no org id
errors, however, I manually verified it is not. Currently, this isn't causing an issue because the query-frontend will create thex-scope-orgid
header withfake
as a value so theAuthenticateUser
middleware is valid. However, this will ensure any changes made to the auth middleware used by the API in the future will also be added to this internalHandler..