Catalyst Authentication 3rd Party Login Module

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

I've read the Catalyst Books, tutorial, cookbook and I must be missing something.

I have a moule MyUsers::Login which takes:

my $user = MyUsers::Login->new(user => $user, pass = $pass);
[download]

It returns undef is the user isn't authenticated and an object if they are.

How would this type of module fit in with Catalyst?

Comment on Catalyst Authentication 3rd Party Login Module Download Code

Replies are listed 'Best First'.
Re: Catalyst Authentication 3rd Party Login Module by Your Mother (Archbishop) on Aug 17, 2010 at 23:34 UTC
It would be more work to make it fit in than to just use the standard Authentication layers. If your user data is already in a database, I'd recommend that. You can do anything you want with Catalyst but the more you stray from community standards, the more you're on your own to figure out how to do it.	[reply]
Re^2: Catalyst Authentication 3rd Party Login Module by awohld (Hermit) on Aug 17, 2010 at 23:35 UTC
Looks like it may be easiest to make a custom Catalyst::Authentication::Credential module like Catalyst::Authentication::Credential::MyApp and on the quick look it appears you need to make an 'authenticate' method which returns a user object.	[reply]
Re: Catalyst Authentication 3rd Party Login Module by trwww (Priest) on Aug 18, 2010 at 05:57 UTC
You can read through the Catalyst::Plugin::Authentication::Internals POD, and then check out the source for the two modules in Catalyst::Authentication::Store::DBIx::Class and that should get you going. Basically check out the existing Catalyst::Authentication::Store modules. Once you set your wrappers up correctly, when you call `$c->user->obj` it will return your `MyUsers::Login` instance.	[reply] [d/l] [select]