This question is locked. New answers and comments are not allowed.
Context
all of our users login to our website using DotNetOpenAuth (twitter, google, facebook)When building the mobile app - i want to make some of the tabs personalized to their profile data. (send and receive data)
For these tabs I need to popup the login window retrieved from server side.
From a desktop perspective I can open up multiple tabs to a website and auth cookie and session cookie are sent across - ensuring my login context is known.
From a mobile perspective how is the context perserved across multiple child browsers on different tabs? - i don't want to user to login multiple times in the same mobile app.
I remember reading how linkedin created a message bridge to only use one childbrowser as bridge.
I cannot just make the whole app a child browser as i do need access to camera to auto upload.
Question
What are the known strategies to migrate functionality existing in web based apps without having to build separate rest api's upfront?How can i quickly integrate a mobile app written with icenium and kendoui mobile with functionality on server side where my controllers have [Authorize] filters attached to ensure the user has the correct roles/permission?