>
> The best idea that we've been able to come up with so far is to move the
> authentication code into a custom subclass of AgaviWebRouting. Any
> thoughts on a Better Way (tm) to do this?
>
You can do this in your user implementation's startup(). Here's a clip
from one of my projects
===============
public function startup()
{
parent::startup();
if (!$this->isAuthenticated() && isset($_SERVER['PHP_AUTH_USER'])) {
try {
$this->login(array(
'mode' => 'http_auth',
'username' => $_SERVER['PHP_AUTH_USER'],
'password' => $_SERVER['PHP_AUTH_PW'],
));
}
catch(AgaviSecurityException $e) {
//no go, continue as usual
}
}
}
==============
-veikko
P.S. In case you don't already have a custom user implementation: extend
AgaviSecurityUser, put the file in app/lib/user/MyUser.class.php, add it
to autoload.xml and configure it in factories.xml.
--
Veikko Mäkinen
[email protected]
044 5910 413
http://blog.veikko.fi
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
