Hi Simon, Just to note my own OpenID proj for ZF isn't on the cards any longer given Andi's notice. However I do feel strongly we need core classes to prevent the buildup of duplicated functionality. For example, Zend_Pdf has a number of byte readers which could be made useful in other classes as a generic Zend_Parser/Zend_String style addition. I didn't even know it existed until I'd done the exact same thing for starting my work on Zend_Yaml as a proposal.
If you're interested in seeing my own implementation of Hmac send me on an email and I'll PM you a copy. I was going to wait for my original OpenID proposal to advance a little more before throwing it in a ring, but it does exist here on an internal repo ;). I have no problem handing out copies under the New BSD. Regards, Paddy Pádraic Brady http://blog.astrumfutura.com http://www.patternsforphp.com ----- Original Message ---- From: Simon Mundy <[EMAIL PROTECTED]> To: Pádraic Brady <[EMAIL PROTECTED]> Cc: Zend Framework General <[email protected]> Sent: Saturday, June 16, 2007 11:51:10 PM Subject: Re: [fw-general] The road to Zend_Service/Auth_Openid Hi Paddy, It sounds like a great starting point. I would welcome the Crypt_xxx libraries, and I know that the Zend_Mail_Smtp transport classes could use the HMAC class to immediately remove their inbuilt code. I've not had much experience with OpenID but with the Zend team backing it I'm sure it would make integration much easier (not unlike the existing high quality components and documentation!). Cheers Hi all, As posted a few months back, I had started working on a PHP5 OpenID library that I wished to port to the framework since it seemed a reasonable addition given our web app focus. Given the complexity of OpenID as a distributed authentication service there are numerous components. Each by itself is actually not that hard, most of the problem is putting them together with a solid set of integration tests. These include wrappers for large integer (> 32 bits) libraries since bcmath alone is awfully slow for this compared to gmp, cryptographic algorithms, and even a separate extensible web service (already proposed on the wiki). The list of possible sub-components that could feasibly get started with include: Zend_Service_Yadis Zend_Crypt_DiffieHellman Zend_Crypt_Rsa Zend_Crypt_Hmac Zend_Crypt_Xtea Zend_Math_BigInteger An actual Zend_Service_Openid would need all of the above as well as general file parsers. I was looking for an opinion as to whether these are acceptable as individual proposals. It seems to make sense rendering OpenID into it's reusable constituent parts rather lumping everything (and inevitably burying/hiding it) into the Openid namespace. I don't want to go spamming the wiki with 6+ proposals until I get a little feedback either :). Any thoughts/comments on this, or OpenID in the ZF in general, are appreciated. :) The primary goal is to implement OpenID 1.1 and 2.0 to the extent necessary to authenticate. The basis of an OpenID server can be considered after. Paddy Pádraic Brady http://blog.astrumfutura.com http://www.patternsforphp.com Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. -- Simon Mundy | Director | PEPTOLAB """ " "" """""" "" "" """"""" " "" """"" " """"" " """""" "" " 202/258 Flinders Lane | Melbourne | Victoria | Australia | 3000 Voice +61 (0) 3 9654 4324 | Mobile 0438 046 061 | Fax +61 (0) 3 9654 4124 http://www.peptolab.com ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news
