Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.6.4

Bug #7537 File storage not working/limited
Submitted: 2006-05-01 14:41 UTC Modified: 2006-12-16 08:30 UTC
From: patrick dot strasser at tugraz dot at Assigned: aashley
Status: Closed Package: Auth (version 1.3.0)
PHP Version: 5.1.2 OS: Linux
Roadmaps: (Not assigned)    
Subscription  


 [2006-05-01 14:41 UTC] patrick dot strasser at tugraz dot at (Patrick Strasser)
Description: ------------ Auth claims in its documantation to support File_Passwd compatibility. In fact, this is limited to CVS password files, unnecessary. Due to its arhitecture to include the containers exclusively only via the Containers subdirectory the only way to work around is to pass a custom Container aobject as storyge type, which can only be a temporary hack. I propose to change the interface to the storage driver to array-style options (with some "file_storage" option) and remove the hardcoded bind to CVS. I'd like to implement the changes if there is interrest for it. (BTW: With Auth_HTTP and File/AuthBasic Backend one can do HTTP Basic Auth in PHP and leave the password maintainance interface to the Hosting Provider) Test script: --------------- Proposed Options: $params = array( "file_storage" => "UNIX", // One of Unix, CVS, // Samba, AuthBasic, AuthDigest, Custom "pwd_file" => "path/to/passwd", "some_option" => "some_value" ); $a = new Auth("File", $params, "myOutput");

Comments

 [2006-05-01 18:36 UTC] aashley at php dot net (Adam Ashley)
Or you could just create Auth/Container/FileUnix.php in your include path and create the appropriate object within. But anyway beside the point. Very interested in seeing your patch to enable control of the type by options. Just remember to maintain backward compatibility
 [2006-08-09 21:45 UTC] aashley at php dot net (Adam Ashley)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.