Loading Profile...
How does OAuth work with non-browser based Consumer applications?
It seems simple and easy, after reading the "get started", to imagine using it in browser applications. How does it work with other kinds of applications? (stand-alone programs, vista gadgets, etc.) There are no redirects there.
Follow this discussion to get notifications on your dashboard.
-
Inappropriate?Well, that's the whole point of OAuth. It offers a standard way for dealing with the flow of browser-based authorization.
For desktop applications or gadgets/widgets, you will invariably need to pop open a browser at some point. Or send someone an SMS. Or somehow get them to confirm their account through a secondary method outside the original app. Fortunately this flow is becoming more common.
To see how this flow actually works, check out these screens from iMovie '08. They don't use OAuth, but it's the same flow:
http://www.flickr.com/photos/factoryj...
I’m confident
-
Inappropriate?As I use it now is that I do open a browser, just for the granting access step.
In my Java app I've added lobo just for that.
I’m frustrated
-
Inappropriate?i can not understand the flow:
http://www.flickr.com/photos/factoryj...1 Comment
Add a comment
-
What don't you understand? Can you be more specific? -
Inappropriate?wrt embedding a browser in your desktop app just of oauth authentication: I'm a bit leery of that solution, because you end up typing your user/pass into the application's browser window - there's no real guarantee that it isn't pinching those details while it's there.
Another way I thought would be to embed a small HTTP server into your application, so when you need to do oauth authentication it fires the request off to the browser, with a callback URL something like http://127.0.0.1:8765/oauthenticated
The port number would probably be chosen randomly or some such.
Would that work?1 Comment Add a comment
-
That sounds reasonable. It's similar to what iPhone apps that use OAuth do with custom schemes.
-
Inappropriate?I'd really like to see a better user experience for iPhone apps that need to use OAuth (for Twitter API for example). Kicking the user to a browser and having to come back to the app is a TERRIBLE user experience no matter how you spin it.
I’m frustrated
EMPLOYEE
