[Catalyst] Extending C::Plugin::Authentication::Store::DBIC for additional constraints

[Doran L. Barton]

Not long ago, Ashvin Kumar proclaimed...
> We had a similar requirement, and came to a slightly different solution 
> than proposed by Fernan. Instead of authenticating on username/password, 
> we authenticated based on user_id/password where user_id is the primary 
> key and guaranteed to be unique.

Thank you very much! That's exactly what I need to make it work. It pays to
think outside the box, sometimes.

On another note: Because I need separate authentication for administrative
users and other users, I am using the "alpha"
Catalyst::Plugin::Authentication module because it supports realms. It took
me some time to wrap my mind around the new concepts employed by this
update of the module, but once I did, everything worked splendidly. 

What is probably going to be most confusing for people who first use the
new Authentication plugin is that many of the configuration variable names
are now application specific. That threw me for a loop for a little while.

A big thank you to the catalyst list for being so helpful!

-=Fozz

-- 
fozz at iodynamics.com is Doran L. Barton, president/CTO, Iodynamics LLC
Iodynamics: IT and Web services by Linux/Open Source specialists
 "Police arrest man found with $4000 in crack"
    -- Newspaper headline
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.scsys.co.uk/pipermail/catalyst/attachments/20070328/96de9fdc/attachment.pgp