PHP-Authentication

PHP-Authentication works like the Tomcat authentication. You give the source to authenticate against (DB, file, XML-RPC, etc.) and the directories that shall be protected, and the class handles the rest. No including of any call to a class method on every page is necessary. You can also use it as if it were a standard Auth-class, using a call to "isLoggedIn" on every page that shall be protected.

Tags Internet Web Site Management Software Development
Licenses PHP
Implementation PHP

Tweet this project Short link

Rss Recent releases

  • Rrelease-mid
  •  11 Mar 2003 02:49
  • Rrelease-after

Changes: Optional logging using the 'logFile' option was added. Session handling was cleaned up, and globals are no longer used. Issues with Windows were fixed, and the isUrlProtected method was optimized to work better under Windows.

  • Rrelease-mid
  •  14 Feb 2003 21:11
  • Rrelease-after

Changes: A new 'ignoreForHash' option was added, and many E_ALL warnings were fixed.

  • Rrelease-mid
  •  17 Sep 2002 05:56
  • Rrelease-after

Changes: This release includes a stable LDAP authentication module.

  • Rrelease-mid
  •  21 Aug 2002 05:49
  • Rrelease-after

Changes: The package can now be installed using the pear installer. Support was added for LDAP, NIS, IMAP, and POP3. The setData method now also takes an array for adding more data at once. Some minor fixes and changes were made.

  • Rrelease-mid
  •  24 May 2002 14:42
  • Rrelease-after

Changes: This release works properly on PHP 4.1 and later. There are some bugfixes. Upadting is recommended, especially if you use the memory container. This release will save GET data for a requested URL, which makes integration of Auth in an existing application even easier.

Rss Recent comments

Rcomment-before 22 Mar 2002 10:24 Rcomment-trans wolfram Rcomment-after

Configuration for each File/Directory desired?
I was thinking if I implement a mechanism, which lets you put a simple xml-file in a directory, or in each file, which lets you determined how the current page/directory shall be protected. Is there any interest for such a thing?
The following example piece of XML, could then go either in the file or directory for which those options shall be set.
Example:
<Auth>
<options>
<!-- protect the current file/directory?? -->
<protect value="no"/>

<!-- define the login page for this file/directory --->
<loginPage value="/path/to/specialLogin.php"/>
</options>
</Auth>

Fa9769a57a5c0968d6bbc0e119566518_thumb

Project Spotlight

WebGUI

A fully featured mod_perl content management system.

No-screenshot

Project Spotlight

geoipgen

An IP network tool for generating geotargeted lists of IP addresses.