Make Mobile Services UserId match the MVC4 OAuth Provider Identity
Why doesn’t my #MobileServices UserId for my Microsoft Account match the ProviderUserId of my MVC4 web app defended by SimpleMembership OAuth?
If I authenticate using my Microsoft Account to my MVC4 web app, I was hoping that I'd be able to start making User authenticated MobileServices REST calls from my MVC server-side code by manually creating a JWT as described by Josh Twist's 12 days of Zumo http://www.thejoyofcode.com/Exploring_custom_identity_in_Mobile_Services_Day_12_.aspx . But, there doesn't appear to be any correlation between the two notions of an ID. So, from my website's login, I don't have enough data to actually make the JWT and have the MobileServices code think that the call is actually me.
I read this forum post and it didn't really help me. I feel that my website and the mobileservice are both using OAuth, so they should both represent me using a common Id.
I want this same story for all the Identity providers, not just Microsoft Account.
Nate Bross commented
This is critical, even for the use case of having a web interface to interact with data in addition to a mobile service. This shouldn't be so complicated.
I think this is a great idea, not only for making zumo calls. But also using the client with own webservices using the same endpoints. And making server side scripting better than the js options we have now. Right now it is just a little too simple for complex server side checks, making the gui client too smart We normally build dumb clients and smart web services, the client we get from zumo is such a dumb client ...