Re:Opauth: Multi-provider authentication framework for PHP, ...
by fryguy on Tuesday May 22, 2012 @07:45PM
(#4010704)
I really wish this was around 2 years ago when I made a site that used openid in PHP. I've dealt with so many nighmares of it I just threw it all away and now send people an email every time they want to log in. How do you deal with supporting every different little configuration of PHP servers? I had huge problems with having to put a hack into the code for lightopenid in order for it to work on my webhost, but that hack broke it on my machine.
[ Parent
| on HN ]
Re:Opauth: Multi-provider authentication framework for PHP, ...
by uzyn on Tuesday May 22, 2012 @11:24PM
(#4011378)
I set a minimum requirement of Opauth Core to be PHP >= 5.2 (though technically it runs fine on >= 5.0) and tries as best as I could to not introduce any unnecessary dependencies, which is the reason why cURL isn't bundled and basic HTTP calls are made through get_file_contents(); and hashing is done through iterations of salted sha1() instead of bundling 3rd party encryption scheme.
Yes, file_get_contents() is not that great, but strategy developers can choose to require cURL if they want, just that Opauth Core doesn't require it.
Re:Opauth: Multi-provider authentication framework for PHP, ...
by rmccue on Wednesday May 23, 2012 @04:28AM
(#4012104)
I'm the developer of Requests (https://requests.ryanmccue.info/) which might be something for you to consider bundling with Opauth. There's a whole host of problems with using file_get_contents on various hosts, hence why cURL is so often used.