CODEWITHSUNDEEP
azureazure-mobile-services
Ryan Alford
Ryan Alford

Reputation: 7594

Azure Mobile App Authorization issue

I am running into an issue with authorization with a new Mobile App service.

I have an old Mobile Service (the predecessor to Mobile Apps), and it works fine with the exact same code. We created a new Mobile Apps service for a new environment, and now it seems to require authorization.

I do not have any [Authorize] attributes in the .Net backend. I don't want any authorization to occur with the API calls.

I believe I have the service setup correctly to disable authorization/authentication. Azure portal

So I'm stuck trying to figure out why I'm getting this response in Postman...

{
   "message": "Authorization has been denied for this request."
}

I believe I have the correct headers that need to be sent with the request from Postman..

Headers

When I try calling the API from my Xamarin Forms app, I get a similar exception,

The request could not be completed. (Unauthorized)

Upvotes: 0

Views: 82

Answers (1)

Eric Hedstrom
Eric Hedstrom

Reputation: 1627

If you are still using the old nuget packages on the server, you still need the x-zumo-application HTTP header as well as the old client nuget packages. You have to update to the new nugets on the client side and server side at the same time. This is why you are seeing the Authorization failures you mentioned.

You may want to keep one service running with the old nuget packages for your existing client base, and have your new service running with the new nuget packages as your clients update. Once your client base has updated, shut down the old service.

Upvotes: 1

Related Questions