Oauth Twitter With Only Consumer Key (not Use Consumer Secret) On Iphone And Android
Solution 1:
I found the solution for myself: Consider the app as an web app, not an mobile app, consists of 3 parts: Facebook/Twitter server, my own app (Apache/PHP) server and browser (the web view on mobile device). With this architecture: my own app server is responsible for authentication and other tasks (post to wall), it store appId, app Secret and userToken, all information, it connect to Facebook/Twitter server directly; the mobile device has role only as an browser agent, it only display a web view pointing to the link that my own server supply, it doesn't store any information
Consider these two documents of Facebook and Twitter about authentication for web app for more detail:
http://developers.facebook.com/docs/guides/web/#login view Authentication section
Solution 2:
No that the way it works with OAuth en Twitter.
Post a Comment for "Oauth Twitter With Only Consumer Key (not Use Consumer Secret) On Iphone And Android"