Azure Mobile Services .NET Adds CORS Support, Better Authentication
Support for cross-origin resource sharing now built in via the ASP.NET Web API.
Microsoft's Azure Mobile Team has an update to its Azure Mobile Services .NET that adds has built-in support for the cross-origin resource sharing specification, as well as improved authentication.
Azure Mobile Services is aimed at mobile developers who want to plug in a cloud-hosted backend to their mobile apps. It uses the ASP.NET Web API and is fully supported in the Visual Studio IDE.
CORS is not enabled by default in Azure Mobile Services .NET, and must be turned on through the Azure management portal or set through the MS_CrossDomainOrigins app setting. Once done, CORS policy can be set at "a per-service, per-controller, or per-action level," blogs Henrik Frystyk Nielsen, principal architect for Microsoft Azure Mobile Services.
Authentication methods have also been improved. Besides authentication via Azure Active Directory, Twitter, Facebook, Google, and Microsoft Account, other authentication methods can be customized. Nielsen writes of an example using LinkedIn authentication that uses an OWIN middleware and registration of that package through the LoginProvider.
Azure Active Directory Authentication has been built in from the beginning, but Nielsen writes that it has been improved "using a server-side flow simplifying client authentication significantly."
Details and download instructions are here.
You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at firstname.lastname@example.org.