[Catalyst] Plugin::Authentication vs Authentiaction
Hello! Trying to use Catalyst::Authentication::Credential::Authen::Simple (::RADIUS, but it does not matter), I've found that I've got two Authentication directories, one is under Plugin. What's worse, Catalyst does not load Catalyst::Authentication::Credential::Authen::Simple automatically, and fails when I put it into use Catalyst qw/ / because it searches only Catalust/Plugin What am I doing wrong? I don't want just put a bunch of symlinks. Catalyst runtime 5.7015 Alex. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
2008/11/10 Alex Povolotsky [EMAIL PROTECTED]: Hello! Trying to use Catalyst::Authentication::Credential::Authen::Simple (::RADIUS, but it does not matter), I've found that I've got two Authentication directories, one is under Plugin. What's worse, Catalyst does not load Catalyst::Authentication::Credential::Authen::Simple automatically, and fails when I put it into use Catalyst qw/ / because it searches only Catalust/Plugin What am I doing wrong? I don't want just put a bunch of symlinks. The fine manual states: If your plugin starts with a name other than Catalyst::Plugin::, you can fully qualify the name by using a unary plus. So you'd do: use Catalyst qw/ Foo # loads C::Plugin::Foo +Catalyst::Authentication::Credential::Authen::Simple # loads the module you wanted /; /joel ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
Joel Bernstein wrote: 2008/11/10 Alex Povolotsky [EMAIL PROTECTED]: Hello! Trying to use Catalyst::Authentication::Credential::Authen::Simple (::RADIUS, but it does not matter), I've found that I've got two Authentication directories, one is under Plugin. What's worse, Catalyst does not load Catalyst::Authentication::Credential::Authen::Simple automatically, and fails when I put it into use Catalyst qw/ / because it searches only Catalust/Plugin What am I doing wrong? I don't want just put a bunch of symlinks. The fine manual states: If your plugin starts with a name other than Catalyst::Plugin::, you can fully qualify the name by using a unary plus. So you'd do: use Catalyst qw/ Foo # loads C::Plugin::Foo +Catalyst::Authentication::Credential::Authen::Simple # loads the module you wanted /; That's not enough. Apparently, Plugin::Authentication is different from Authentication, and slightly not compartible. Alex. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
2008/11/10 Alex Povolotsky [EMAIL PROTECTED]: Joel Bernstein wrote: The fine manual states: If your plugin starts with a name other than Catalyst::Plugin::, you can fully qualify the name by using a unary plus. So you'd do: use Catalyst qw/ Foo # loads C::Plugin::Foo +Catalyst::Authentication::Credential::Authen::Simple # loads the module you wanted /; That's not enough. Apparently, Plugin::Authentication is different from Authentication, and slightly not compartible. Er... what? That's nothing to do with what you asked. Why are you loading Plugin::Authentication if you don't want to use it? I answered your question of how do I load C::Authentication::Blah via use Catalyst qw();. If you'd like a different answer, ask a different question. /joel ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
2008/11/10 Joel Bernstein [EMAIL PROTECTED]: 2008/11/10 Alex Povolotsky [EMAIL PROTECTED]: Joel Bernstein wrote: The fine manual states: If your plugin starts with a name other than Catalyst::Plugin::, you can fully qualify the name by using a unary plus. So you'd do: use Catalyst qw/ Foo # loads C::Plugin::Foo +Catalyst::Authentication::Credential::Authen::Simple # loads the module you wanted /; That's not enough. Apparently, Plugin::Authentication is different from Authentication, and slightly not compartible. Er... what? That's nothing to do with what you asked. Why are you loading Plugin::Authentication if you don't want to use it? I answered your question of how do I load C::Authentication::Blah via use Catalyst qw();. If you'd like a different answer, ask a different question. So, strictly speaking, my answer to your question of how do I load a plugin not called C::Plugin::Blah was accurate. In fact, interms of how to load the auth backends, it's completely false. And I do understand your question now. The answer is, Catalyst::Authentication::Credential::Authen::Simple is not a plugin. So you don't load it like a Plugin since you *don't* want MyApp-isa(Catalyst::Authentication::Credential::Authen::Simple) to be true. What you do is, load C::Plugin::Authentication, and then in your application config you have a section for Plugin::Authentication which tells it, among other things, which backends for its various modular features to load. See TFM for C::Plugin::Authentication and the Cookbook. HTH, and sorry for the confusion earlier. /joel ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
Joel Bernstein wrote: 2008/11/10 Alex Povolotsky [EMAIL PROTECTED]: Joel Bernstein wrote: The fine manual states: If your plugin starts with a name other than Catalyst::Plugin::, you can fully qualify the name by using a unary plus. So you'd do: use Catalyst qw/ Foo # loads C::Plugin::Foo +Catalyst::Authentication::Credential::Authen::Simple # loads the module you wanted /; That's not enough. Apparently, Plugin::Authentication is different from Authentication, and slightly not compartible. Er... what? That's nothing to do with what you asked. Why are you loading Plugin::Authentication if you don't want to use it? I answered your question of how do I load C::Authentication::Blah via use Catalyst qw();. If you'd like a different answer, ask a different question. Reasking. I did not want just load plugin for fun. I wanted to use two authentication realms, one with Credential::Password and Store::DBIx::Class, the other with Credential::Authen::Simple and Store::Null However, since I have (don't know why exactly) both Catalyst::Authentication and Catalyst::Plugin::Authentication, I seems to have problems setting all of those to work together. Alex. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
Alex Povolotsky escribió: Hello! Trying to use Catalyst::Authentication::Credential::Authen::Simple (::RADIUS, but it does not matter), I've found that I've got two diAuthentication rectories, one is under Plugin. What's worse, Catalyst does not load Catalyst::Authentication::Credential::Authen::Simple automatically, and fails when I put it into use Catalyst qw/ / because it searches only Catalust/Plugin What happens when you run Catalyst::Authentication::Credential::Authen::Simple tests on your setup? In the tests should be a mini app that authenticates with C::A::C::Authen::Simple (see the t/lib/AuthTestApp2 and AuthTestApp3). See the code if you're having problems. Also, in examples dir there is an example application. Are you on the latest version of Catalyst::Plugin::Authentication? I think your problems are because the Authentication plugin components where moved to a new namespace (without Plugin in the middle). Note: Patches welcome ;) Jose Luis Martinez [EMAIL PROTECTED] ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
On Nov 10, 2008, at 8:46 AM, Alex Povolotsky wrote: That's not enough. Apparently, Plugin::Authentication is different from Authentication, and slightly not compartible. Alex, The Authentication modules underwent a significant overhaul a while back. In the old scheme, there were many authentication plugins. In the new scheme, the only plugin is Catalyst::Plugin::Authentication There are a few Catalyst::Plugin::Authentication modules that provide some backwards compatibility but I believe that at this point, Catalyst::Plugin::Authentication::* is deprecated, and the older Plugins likely won't work with the new scheme. So if you have the choice between Catalyst::Authentication::something and Catalyst::Plugin::Authentication::something, use the former and not the later. In the new scheme, the storage and credential modules are brought in through the configuration of Catalyst::Plugin::Authentication - take a look at its documentation to see how this is done. They don't appear in the plugin list at all, only Catalyst::Plugin::Authentication does Catalyst::Plugin::Authentication's documentation gives a good overview of how to use it and what to pay attention to and what to ignore: http://search.cpan.org/dist/Catalyst-Plugin-Authentication/lib/Catalyst/Plugin/Authentication.pm There's no reason that Catalyst would load Catalyst::Authentication::Credential::Authen::Simple automatically - only some users need it - and putting it in the plugin list won't help because it's not a plugin. Its documentation shows how to configure Catalyst::Plugin::Authentication to use it http://search.cpan.org/dist/Catalyst-Authentication-Credential-Authen-Simple/lib/Catalyst/Authentication/Credential/Authen/Simple.pm - john romkey http://dot.romkey.com/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
John Romkey wrote: On Nov 10, 2008, at 8:46 AM, Alex Povolotsky wrote: That's not enough. Apparently, Plugin::Authentication is different from Authentication, and slightly not compartible. Alex, The Authentication modules underwent a significant overhaul a while back. In the old scheme, there were many authentication plugins. In the new scheme, the only plugin is Catalyst::Plugin::Authentication Thanks everyone. It was, of course, my fault. I've used login instead of username in attempt to authenticate. Alex. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Plugin::Authentication vs Authentiaction
John Romkey wrote: On Nov 10, 2008, at 8:46 AM, Alex Povolotsky wrote: That's not enough. Apparently, Plugin::Authentication is different from Authentication, and slightly not compartible. Alex, The Authentication modules underwent a significant overhaul a while back. In the old scheme, there were many authentication plugins. In the new scheme, the only plugin is Catalyst::Plugin::Authentication There are a few Catalyst::Plugin::Authentication modules that provide some backwards compatibility but I believe that at this point, Catalyst::Plugin::Authentication::* is deprecated, and the older Plugins likely won't work with the new scheme. So if you have the choice between Catalyst::Authentication::something and Catalyst::Plugin::Authentication::something, use the former and not the later. In the new scheme, the storage and credential modules are brought in through the configuration of Catalyst::Plugin::Authentication - take a look at its documentation to see how this is done. They don't appear in the plugin list at all, only Catalyst::Plugin::Authentication does Thanks a lot, things become much less clear. Now, after some cleaning up of configs, everything gets loaded fine; however, [debug] Unable to locate user matching user info provided while realm has store of Null, and find_user has no ability to fail. I'm trying to understand this. Alex. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
