简体   繁体   中英

Azure MobileApp Custom Authentication VS Asp.Net Identity

Microsoft claims to provide OOB functionality for custom authentication. I started using this library, I am surprised that only feature available from this library is to generate token. Thats all! I believe Default template for Web API Asp.Net Identity is a better implementation and provides complete functionality.

Mobile App has to be something better than close to metal Web API. Am I missing something here, could you please show me the right direction?

References: http://www.newventuresoftware.com/blog/custom-authentication-with-azure-mobile-apps/

Azure Mobile Apps provides a turnkey solution, where by simply configuring the identity providers you want to support (eg Azure Active Directory, Microsoft Account, Facebook, Google, etc.) you can enable authentication.

This document provides an overview, as well as links to details and technical resources:

https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-auth/

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM