Chapter 4
Authentication Options in WAMS
IN THIS CHAPTER:
- Configure your mobile service to support authentication
- Set up the various authentication providers to support your mobile service
- Troubleshoot issues related to authentication and your mobile service
WROX.COM CODE DOWNLOADS FOR THIS CHAPTER
The wrox.com code downloads for this chapter are found at http://www.wrox.com/go/windowsazuremobileservices on the Download Code tab. The code is in the Chapter 4 download and individually named according to the names throughout the chapter.
To this point, you’ve seen how to access your mobile service from the client side, as well as how to implement server-side scripts to handle validation and other advanced functionality. However, to take advantage of these capabilities, in many cases, you also need to be able to identify the user who is making the request.
As of the time of writing, Windows Azure Mobile Services (WAMS) supports authentication from four different providers: Facebook, Google, Microsoft Account (formerly Microsoft Live ID), and Twitter. From the perspective of creating client-side code that performs this authentication, the steps are very straightforward. This chapter covers a number of topics related to authentication. First, you learn some of the fundamental ideas related to authentication. This is not because you need to have this information to utilize WAMS authentication, but because when something goes wrong in the authentication process, it’s a very good idea ...
Get Windows Azure Mobile Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
