Agreeing with Morten, it's difficult to have a OAuth provider library be gapless because the storage problem.
HTTP_OAuth takes the approach of no data store interfaces and assumes the developer will have other methods of looking up a consumer application record in the DB, saving that record, saving a request token, etc. Here is what it looks like in the proposal: http://pear.php.net/pepr/pepr-proposal-show.php?id=607 -jeff On Nov 12, 2009, at 8:02 AM, rob ganly wrote: > > hi morten, > > thanks for your reply. > > i recognise that there's nothing 'missing' from the library but it > requires a fair bit of complimentary coding to be done in order to > implement it, hence 'there are a few gaps to fill', however i can > appreciate your point regarding the hooks and data-storage. > > what about 1.0a, does it support that yet? if not do you know if > anyone's developing a patch for it? > > rob > > On Nov 12, 3:36 pm, Morten Fangel <fan...@sevengoslings.net> wrote: >> Hi, >> >> There is nothing "missing" in thehttp://oauth.googlecode.com/svn/code/php/ >> library to implement either a consumer or a service-provider.. >> >> Obviously you need to code up your own data-storage and add in the >> hooks at the pages you want to be your endpoints, but this is just so >> you have full flexibility or where and how do to stuff.. >> >> For a fully working sample implementation of a service-provider, you >> can see the code for my OAuth >> Playgroundhttp://github.com/fangel/oauth-sandbox >> >> Specifically the data-storage:http://github.com/fangel/oauth- >> sandbox/blob/master/library/DataStorag... >> and the end-points page:http://github.com/fangel/oauth-sandbox/blob/ >> master/api.php >> >> -- >> >> I need to fix a bug related to interoperability with Joe Stumps >> Python >> library, after which I will get all my patches submitted.. I just >> need >> to have some free time to do it.. >> >> -Morten >> >> On Nov 12, 2009, at 3:54 AM, rob ganly wrote: >> >> >> >>> hi all, >> >>> i'm currently implementing the version that joseph mentioned, i.e. >>> http://oauth.googlecode.com/svn/code/php/ >> >>> i need to implement both a consumer and a provider. obviously the >>> most >>> involved part is creating the provider. >> >>> obviously there are a few gaps to fill in the above library before >>> it >>> can be fully implemented and it is a bit of a worry that it has >>> pretty >>> stagnant for 6 months (although i note morten's comments on recent >>> activity). however seeing as it doesn't yet support 1.0a and >>> requires >>> some extra coding in order to do so i think that i might actually >>> switch to using the other lib that joseph mentioned:http:// >>> code.google.com/p/oauth-php/ >> >>> it seems there's still the lack of a distinct leading library >>> complete >>> with documentation and examples. >> >>> thus, i'd be interested in learning what lib. people would choose if >>> they personally were implementing both a provider and a consumer? >> >>> best, >> >>> rob ganly >> >>> On Nov 11, 7:54 pm, Nicholas Granado <ngran...@gmail.com> wrote: >>>> I don't know if anyone has mentioned EpiOAuth. >> >>>> http://github.com/jmathai/twitter-async >> >>>> --- >>>> Nicholas Granado >>>> twitter: heatxsink >>>> web: http://nickgranado.com >>>> email: ngran...@gmail.com >> >>>> On Wed, Nov 11, 2009 at 11:40 AM, Melvin Carvalho >>>> <melvincarva...@gmail.com>wrote: >> >>>>> On Wed, Nov 11, 2009 at 5:58 PM, camilo_u <morci...@gmail.com> >>>>> wrote: >> >>>>>> There is a Zend Framework proposal currently testing called >>>>>> Zend_OAuth: >> >>>>>> http://framework.zend.com/wiki/pages/viewpage.action?pageId=37957 >> >>>>>> You can take a look at the code here: >> >>>>> http://framework.zend.com/svn/framework/standard/incubator/library/Ze >>>>> ... >> >>>>>> One of the proposer, Pádraic Brady, has a sample implementation >>>>>> with >>>>>> Twitter: >> >>>>> http://blog.astrumfutura.com/archives/411-Writing-A-Simple-Twitter-Cl >>>>> ... >> >>>>> Also recently came across this twitter impl. also on github >> >>>>> http://github.com/abraham/twitteroauth >> >>>>>> As far as i know it's ready with the OAuth Core 1.0 Revision A, >>>>>> and >>>>>> hopefully it will be availabe on the Zend Framwork 1.10, so this >>>>>> will >>>>>> be a very common library soon. >> >>>>>> Regards, >> >>>>>> Camilo Usuga >> >>>>>> On 10 nov, 16:56, Jeff Hodsdon <jeffhods...@gmail.com> wrote: >>>>>>> There is also a PEAR library,http://pear.php.net/package/HTTP_OAuth >>>>>>> , >>>>>>> which has classes for being a provider. >> >>>>>>> -jeff >>>>>>> On Nov 6, 2009, at 8:21 AM, Joseph Smarr wrote: >> >>>>>>>> Thanks Morten. I'd really encourage you to finish up those >>>>>>>> patches >>>>>>>> and submit them, since I think a lot of people do use that >>>>>>>> OAuth >>>>>>>> library. I'm happy to do a code review or otherwise take a look >>>>>>>> at >>>>>>>> it if that's useful to you. >> >>>>>>>> Thanks, js >> >>>>>>>> On Fri, Nov 6, 2009 at 12:34 AM, Morten Fangel < >>>>> fan...@sevengoslings.net >>>>>>>>> wrote: >>>>>>>> Hi, >> >>>>>>>> I did some of the most recent patches on thehttp:// >>>>> oauth.googlecode.com/svn/code/php/ >>>>>>>> library.. And speaking of two-legged and rev. a. - I actually >>>>>>>> have >>>>>>>> done work on those, I just haven't had time to finish up on the >>>>>>>> work >>>>>>>> (but they are running on the OAuth Sandbox which can be found >>>>> athttp://oauth-sandbox.sevengoslings.net >>>>>>>> - so it does work) >> >>>>>>>> Just to let people know that the library isn't dead.. ;) >> >>>>>>>> -Morten >> >>>>>>>> On Nov 5, 2009, at 9:49 PM, Joseph Smarr wrote: >> >>>>>>>>> It seems like there are several actively maintained PHP OAuth >>>>>>>>> libraries, and it's not clear to me which are most up-to-date >>>>>>>>> and/ >>>>>>>>> or widely used. The oauth.net/code page mainly featureshttp:// >>>>> oauth.googlecode.com/svn/code/php/ >>>>>>>>> which hasn't been updated since May 18, 2009. There's >>>>>>>>> alsohttp:// >>>>> code.google.com/p/oauth-php/ >>>>>>>>> which looks more complicated but also more up-to-date. And >>>>>>>>> there's >>>>>>>>> alsohttp://pecl.php.net/oauthwhichisa C extension for OAuth >>>>>>>>> that it looks like Rasmus et al have bene updating recently. >> >>>>>>>>> Personally, I like (and use) >>>>> http://oauth.googlecode.com/svn/code/php/ >>>>>>>>> because it's simple (just one file), and I believe shindig- >>>>>>>>> php >>>>>>>>> uses it too, but I don't think it has support for OAuth 1.0a >>>>>>>>> or two- >>>>>>>>> legged OAuth, both of which are very standard now. I also >>>>>>>>> recall >>>>>>>>> fixing a bunch of bugs in it that may or may not have ever >>>>>>>>> landed >>>>>>>>> in the tree. >> >>>>>>>>> So, should I add 1.0a and 2-legged support to this lib? If so, >>>>>>>>> will >>>>>>>>> someone review and patch it and/or make me a committer? Has >>>>>>>>> anyone >>>>>>>>> else already made these updates and just not shared it back? >>>>>>>>> Or is >>>>>>>>> one of these other libraries now the "de facto standard PHP >>>>>>>>> lib", >>>>>>>>> in which case shouldn't it be listed on oauth.net/code under >>>>>>>>> PHP? >> >>>>>>>>> Thanks, js >> >> > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google > Groups "OAuth" group. > To post to this group, send email to oauth@googlegroups.com > To unsubscribe from this group, send email to > oauth+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/oauth?hl=en > -~----------~----~----~----~------~----~------~--~--- > -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oa...@googlegroups.com. To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/oauth?hl=.
