dasiths
commented
4 years ago I can't say for sure without looking at your code. Is the 401 being returned from your own code (i.e. Controller with Authorization attribute) or from a downstream API?
The best way to test it would be to do something like this in your code
[Route("api/[controller]")]
[ApiController]
public class AuthTestController : ControllerBase
{
// GET api/values
[HttpGet]
public ActionResult<object> Get()
{
var headers = Request.Headers
.Select(h => new {name = h.Key, value = h.Value})
.ToList();
var userClaims = HttpContext.User.Claims
.Select(claim => new {name = claim.Type, value = claim.Value})
.ToList();
return new
{
Headers = headers,
Claims = userClaims
};
}
}- Follow the ReadMe file from this repo and add NEasyAuthMiddleware in. Then add the above code snippet for the controller.
- Deploy it to an app service. (Configured to work with Google federated sign in)
- Then hit https://yourwebsitename.azurewebsites.net/api/AuthTest and see what it returns. If it has all the claims and headers you expect then we can be certain the middleware works.
- If there is a header but isn't mapped to a claim then you will have have to write a custom mapper as shown in the readme.
- The token will be in a claim or in the header hence you won't need to call
.auth/login/googleto get it AFAIK. You can then simply attach that as an authorization header in a downstream API call.
HeinA
'ello
While testing with postman, I always get a 401 Unauthorized.
I'm testing this for an Api that I want to call from Unity using Google sign-in.
I pass the Authentication Token I get from the ".auth/login/google" endpoint on my App Service to my API in the X-ZUMO-AUTH header.
Am I misunderstanding something?
Thanx Hein