Hey all - Just a followup to the list.
The issue here is that Michael's module did not cal the
default_auth_store routine - which meant it was never set up as the
default store.
There is a side effect of the old configuration method for multiple
stores that caused his class-name to be used in
this does break my custom authentication. i am still investigating
why..
On Jul 7, 2007, at 12:50 PM, Jay K wrote:
Hey all,
Big news! With the most excellent assistance of J. Shirley and
Nilson Santos Figueiredo Junior - The new C::P::Authentication
finally has all it's tests and, we
the short answer is it does not call my store's get_user method, despite
__PACKAGE__-config(
authentication = { store =
'MyApp::Plugin::Authentication::DBI::User'}
);
the error i get is:
[debug] find_user: unable to locate a store matching the requested realm
the new docs suggest
empty hashref: {}
some details about MyApp:
use MyApp::Plugin::Authentication::DBI::User;# $c-user class
use Catalyst (
# ...
'Authentication', # Implements $c-user
'+MyApp::Plugin::Authentication::DBI', # Implements $c-login
# ...
Hey all,
Big news! With the most excellent assistance of J. Shirley and
Nilson Santos Figueiredo Junior - The new C::P::Authentication
finally has all it's tests and, we feel, is ready for release.
Thus - the Release Candidate is now on CPAN at:
