-
Notifications
You must be signed in to change notification settings - Fork 340
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
Unable to pass Authorization header #1352
Comments
Could you share some more information about what you're calling and how? Bonus points if you could share a simple repro project! |
@JulianJJ I put together my own sample project and was unable to reproduce what you're seeing. Again, your own repro would be helpful, but in lieu of that, could you answer a couple of questions for me:
|
@WhitWaldo Thanks for the reply. API in Service B [Authorize] } The Service B get 401 Unauthorized as the Bearer token is never passed along with the request. I can see I get test-api-key in the request header in Service B but not the authorization header. |
@JulianJJ Thank you for the additional details. I added a unit test to the suite to validate that all headers passed in with an I then created two simple ASP.NET Core repro projects in which I passed a GET request from Service A to Service B, creating the request as you did via Could you glob together a minimal repro project so I might step through it? Is it possible that you have anything on Service B that's stripping the headers off? |
@JulianJJ Were you able to put a repro project together for this bug? |
@WhitWaldo Not yet.. Will let you know soon |
Expected Behavior
When I pass Authorization header I should receive in the target API just like dapr api key
Actual Behavior
Authorization header is not received in the target API
The text was updated successfully, but these errors were encountered: