title: Authentication after migrating to App Services Mobile App: uid vs sid
body: <p>I've migrated form Azure Mobile Services to the new App Services Mobile App, and I'm using the new AMS 2.0.0-beta on the client-side.</p>
  
  <p>I have two providers (currently) implemented for OAuth 2.0: Google and Twitter.</p>
  
  <p>Previously, I was able to get the provider token via a claim in the principal on the server, and there would be a uid (unique id) claim that would be either "Google:123456789" or "Twitter:123456789010" (or however many alphanumerics). I believe the MobileServiceClient.UserId also exposed this as well.</p>
  
  <p>Now, after I've migrated to the new App Services Mobile App (and I'm using the Preview Portal now, which for the most part is pretty awesome), there is no longer a uid claim, but rather a single sid (session id) claim, something like: "sid:ABCDEFGHIJKLMNOPQRSTUVWXYZ", no matter which provider I log in with. When I looked on the client-side at the MobileServiceClient.UserId value, it also gives this "sid" value.</p>
  
  <p>The point is that previously the uid token could uniquely identify a user. Now it is the same for all users across all providers!</p>
  
  <p>How can I get the provider token with the App Services Mobile App that I was previously able to get with Azure Mobile Services?</p>
  
  <p>Also, could anyone point me to the source code for the Azure Mobile Services 2.0.0-beta? Is it open source? I can't seem to find it on GitHub. </p>
  
  <p>Edit: Here is a screenshot of the User on the server side:
  <img src="https://i.stack.imgur.com/HO9p7.png" alt="enter image description here"></p>