<commit_before>---
layout: post
title: "Authenticate Azure Mobile Services Apps with Everything using Auth0"
date: 2013-03-17 11:00
author: 
  name: <NAME>
  mail: <EMAIL>
---

[Windows Azure Mobile Services](http://www.windowsazure.com/en-us/develop/mobile/) (WAMS) is a really neat technology by Microsoft to get you started very quickly with simple mobile apps. It's a _"Mobile Backend as a Service"_. It also provides a nice extensibility model for more advanced scenarios with server-side JavaScript. 

WAMS already ships with support for single-sign-on with social identity providers (e.g Facebook, LiveID), but no support for enterprise providers: Google Apps, Office 365 and Active Directory; or even custom SQL user databases. Even for social providers, it currently doesn't allow finer grain control on what information the user has to consent to disclose. 

For Microsoft Accounts (LiveID), for example, WAMS will ask the user for the following rights: name, gender, display picture, contacts and friends. You might not need all these, and you might turn away customers by asking to much.

Auth0 addresses these two issues:

- You can connect to __any__ supported identity provider: social and enterprise<commit_msg>Fixed typos<commit_after>---
layout: post
title: "Authenticate Azure Mobile Services Apps with Everything using Auth0"
date: 2013-03-17 11:00
author: 
  name: <NAME>
  mail: <EMAIL>
---

[Windows Azure Mobile Services](http://www.windowsazure.com/en-us/develop/mobile/) (WAMS) is a really neat technology by Microsoft to get you started very quickly with simple mobile apps. It's a _"Mobile Backend as a Service"_. It also provides a nice extensibility model for more advanced scenarios with server-side JavaScript. 

WAMS already ships with support for single-sign-on with social identity providers (e.g Facebook, LiveID), but no support for enterprise providers: Google Apps, Office 365 and Active Directory; or even custom SQL user databases. Even for social providers, it currently doesn't allow finer grain control on what information the user has to consent to disclose. 

For Microsoft Accounts (LiveID), for example, WAMS will ask the user for the following rights: name, gender, display picture, contacts and friends. You might not need all these, and you might turn away customers by asking too much.

Auth0 addresses these two issues:

- You can connect to __any__ supported identity provider: social and enterprise
{'fraction_non_alphanumeric': 0.061149612719119444, 'fraction_numerical': 0.013860578883000407, 'mean_word_length': 4.706976744186046, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5222169', 'n_tokens_mistral': 637, 'n_tokens_neox': 586, 'n_words': 344}