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

Unable to pass Authorization header #1352

Open
JulianJJ opened this issue Sep 27, 2024 · 6 comments · Fixed by #1355
Open

Unable to pass Authorization header #1352

JulianJJ opened this issue Sep 27, 2024 · 6 comments · Fixed by #1355
Labels
area/client kind/bug Something isn't working

Comments

@JulianJJ
Copy link

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

@JulianJJ JulianJJ added the kind/bug Something isn't working label Sep 27, 2024
@WhitWaldo
Copy link
Contributor

Could you share some more information about what you're calling and how? Bonus points if you could share a simple repro project!

@WhitWaldo
Copy link
Contributor

@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:

  • Could you confirm that you're using InvokeMethodAsync and passing it an HttpRequestMessage decorated with the Authorization header?
  • Does the receiving API receive the request at all?
  • Do you see any headers on the target API? Is it only missing the Authorization header?

@JulianJJ
Copy link
Author

JulianJJ commented Oct 7, 2024

@WhitWaldo Thanks for the reply.
Here is the part of the code..
Source Call from backend of Service A
var request = _daprClient.CreateInvokeMethodRequest(method, "serviceb", methodName, new List<KeyValuePair<string, string>>(), request);
req.Headers.Add("test-api-key","test"); //pass
req.Headers.Add("authorization,"Bearer tokenstring"); //Doesn't work
req.Headers.Authorization = new AuthenticationHeaderValue("Bearer ", "tokenstring"); //Doesn't work
var result = await _serviceClient.InvokeMethodAsync(req, token);

API in Service B

[Authorize]
public class TestController : ControllerBase
{
[HttpGet]
public IActionResult Get()
{
return Ok("Pass");
}

}

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.

@WhitWaldo
Copy link
Contributor

WhitWaldo commented Oct 7, 2024

@JulianJJ Thank you for the additional details.

I added a unit test to the suite to validate that all headers passed in with an HttpRequestMessage to InvokeMethodAsync on the client are present in the request it makes via the HTTP client and that's passing as expected.

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 _daprClient.CreateInvokeMethodRequest and supplementing it with "test-api-key:test", "Authorization:Bearer abc123" and "Accept:application/json" and all headers are present when I break on the inbound request to my Service B controller. We should definitely add this as an end-to-end test to validate, but I'm afraid I'm simply unable to reproduce the problem you're describing.

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?

@WhitWaldo
Copy link
Contributor

@JulianJJ Were you able to put a repro project together for this bug?

@JulianJJ
Copy link
Author

@WhitWaldo Not yet.. Will let you know soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/client kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants