Is this for login alone or do you return API keys (and are the keys for the provider service or for OAuth.io)?
OAuth.io - OAuth that just works.
11–20 of 54 posts
Re: OAuth.io - OAuth that just works.
#12Re: OAuth.io - OAuth that just works.
#13Re: OAuth.io - OAuth that just works.
#14Re: OAuth.io - OAuth that just works.
#15There's no shortage of simple OAuth consumer libraries out there, what I really want to see is a simple way to set up my app as an OAuth _provider_. As far as I know there's nothing out there to make that simple yet.
Re: OAuth.io - OAuth that just works.
#16Re: OAuth.io - OAuth that just works.
#17Re: OAuth.io - OAuth that just works.
#18There's no shortage of simple OAuth consumer libraries out there, what I really want to see is a simple way to set up my app as an OAuth _provider_. As far as I know there's nothing out there to make that simple yet.
However I should say that our framework takes a different philosophy. We believe that web apps shouldn't have to ask for OAuth access at all just to personalize the experience for you. They can ask the provider to display to you your name and everything else, in iframes that they can't get visibility into. Although I dislike patents, the whole system was non obvious enough to file one for the investors: http://www.faqs.org/patents/app/20120110469#b
We use oauth mainly for single sign-on, and the access permissions are actually a special case of an app requesting access to various streams you publish. In our framework, the app simply has a user id just like any other user, and can request access to your stream just like any other user. You can put users into friends, family, admins or any other roles, and then give them permissions on various streams.
Re: OAuth.io - OAuth that just works.
#19Re: OAuth.io - OAuth that just works.
#20I am now at step 125. Still watching...