{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 老娘就宠你 的问题《Azure Mobile Services and Azure Web Site integrati》','https://www.manongdao.com/q-923276.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I am hosting a REST endpoint using the ASP.NET Web.Api in a Windows Azure web site. I want to allow authenticated access to this api from mobile devices. The Azure mobile services seems to have easy authentication providers as well as other goodies such as push notifications.
What would be an effective strategy for using the two in tandem, the web sites to host the REST endpoint and the mobile services to do authentication and push notifications?
Before you think about anything ahead, CRUD operations which are initiated from the app only receive push notifications, for example, if you manually enter tuples in a database or through code, they won't execute the server scripts and thus no notifications will be send.
About authentication, you may send a token(can be primitive, do not expect to hash or encrypt, if however you use a database to store hashes) once mobile services authenticate your user and then only call the web api's. The thing is the server scripts are fairly limited and can't perform hashing, encryption or other computes which you may expect.