3 package Catalyst::Plugin::Authentication;
5 use base qw/Class::Accessor::Fast Class::Data::Inheritable/;
8 __PACKAGE__->mk_accessors(qw/_user/);
17 # this optimization breaks under Template::Toolkit
18 # use user_exists instead
21 # constant->import(have_want => eval { require Want });
24 our $VERSION = "0.10001";
26 sub set_authenticated {
27 my ( $c, $user, $realmname ) = @_;
30 $c->request->{user} = $user; # compatibility kludge
33 $realmname = 'default';
36 if ( $c->isa("Catalyst::Plugin::Session")
37 and $c->config->{authentication}{use_session}
38 and $user->supports("session") )
40 $c->save_user_in_session($user, $realmname);
42 $user->auth_realm($realmname);
43 $user->store(ref($c->auth_realms->{$realmname}{'store'}));
45 $c->NEXT::set_authenticated($user, $realmname);
55 if ( defined($c->_user) ) {
58 return $c->auth_restore_user;
62 # change this to allow specification of a realm - to verify the user is part of that realm
63 # in addition to verifying that they exist.
66 return defined($c->_user) || defined($c->_user_in_session);
69 # works like user_exists - except only returns true if user
70 # exists AND is in the realm requested.
72 my ($c, $realmname) = @_;
74 if (defined($c->_user)) {
75 return ($c->_user->auth_realm eq $realmname);
76 } elsif (defined($c->_user_in_session)) {
77 return ($c->session->{__user_realm} eq $realmname);
83 sub save_user_in_session {
84 my ( $c, $user, $realmname ) = @_;
86 $c->session->{__user_realm} = $realmname;
88 # we want to ask the store for a user prepared for the session.
89 # but older modules split this functionality between the user and the
90 # store. We try the store first. If not, we use the old method.
91 my $realm = $c->get_auth_realm($realmname);
92 if ($realm->{'store'}->can('for_session')) {
93 $c->session->{__user} = $realm->{'store'}->for_session($c, $user);
95 $c->session->{__user} = $user->for_session;
105 $c->isa("Catalyst::Plugin::Session")
106 and $c->config->{authentication}{use_session}
107 and $c->session_is_valid
109 delete @{ $c->session }{qw/__user __user_realm/};
112 $c->NEXT::logout(@_);
116 my ( $c, $userinfo, $realmname ) = @_;
118 $realmname ||= 'default';
119 my $realm = $c->get_auth_realm($realmname);
120 if ( $realm->{'store'} ) {
121 return $realm->{'store'}->find_user($userinfo, $c);
123 $c->log->debug('find_user: unable to locate a store matching the requested realm');
128 sub _user_in_session {
132 $c->isa("Catalyst::Plugin::Session")
133 and $c->config->{authentication}{use_session}
134 and $c->session_is_valid;
136 return $c->session->{__user};
139 sub auth_restore_user {
140 my ( $c, $frozen_user, $realmname ) = @_;
142 $frozen_user ||= $c->_user_in_session;
143 return unless defined($frozen_user);
145 $realmname ||= $c->session->{__user_realm};
146 return unless $realmname; # FIXME die unless? This is an internal inconsistency
148 my $realm = $c->get_auth_realm($realmname);
149 $c->_user( my $user = $realm->{'store'}->from_session( $c, $frozen_user ) );
151 # this sets the realm the user originated in.
152 $user->auth_realm($realmname);
153 ## compatibility - some pre 0.10 store / credentials may need the store name,
154 ## this is not used by the current api in any form.
155 $user->store(ref($c->auth_realms->{$realmname}{'store'}));
161 # we can't actually do our setup in setup because the model has not yet been loaded.
162 # So we have to trigger off of setup_finished. :-(
166 $app->_authentication_initialize();
167 $app->NEXT::setup(@_);
170 ## the actual initialization routine. whee.
171 sub _authentication_initialize {
174 ## let's avoid recreating / configuring everything if we have already done it, eh?
175 if ($app->can('_auth_realms')) { return };
177 ## make classdata where it is used.
178 $app->mk_classdata( '_auth_realms' => {});
180 my $cfg = $app->config->{'authentication'} ||= {};
182 $cfg->{use_session} = 1;
184 if (exists($cfg->{'realms'})) {
185 foreach my $realm (keys %{$cfg->{'realms'}}) {
186 $app->setup_auth_realm($realm, $cfg->{'realms'}{$realm});
188 # if we have a 'default-realm' in the config hash and we don't already
189 # have a realm called 'default', we point default at the realm specified
190 if (exists($cfg->{'default_realm'}) && !$app->get_auth_realm('default')) {
191 $app->_set_default_auth_realm($cfg->{'default_realm'});
195 ## BACKWARDS COMPATIBILITY - if realms is not defined - then we are probably dealing
196 ## with an old-school config. The only caveat here is that we must add a classname
198 ## also - we have to treat {store} as {stores}{default} - because
199 ## while it is not a clear as a valid config in the docs, it
200 ## is functional with the old api. Whee!
201 if (exists($cfg->{'store'}) && !exists($cfg->{'stores'}{'default'})) {
202 $cfg->{'stores'}{'default'} = $cfg->{'store'};
205 foreach my $storename (keys %{$cfg->{'stores'}}) {
207 store => { class => $cfg->{'stores'}{$storename} },
209 $app->setup_auth_realm($storename, $realmcfg);
216 sub setup_auth_realm {
217 my ($app, $realmname, $config) = @_;
219 $app->log->debug("Setting up auth realm $realmname") if $app->debug;
220 if (!exists($config->{'store'}{'class'})) {
221 Carp::croak "Couldn't setup the authentication realm named '$realmname', no class defined";
225 my $storeclass = $config->{'store'}{'class'};
227 ## follow catalyst class naming - a + prefix means a fully qualified class, otherwise it's
228 ## taken to mean C::P::A::Store::(specifiedclass)
229 if ($storeclass !~ /^\+(.*)$/ ) {
230 $storeclass = "Catalyst::Plugin::Authentication::Store::${storeclass}";
236 # a little niceness - since most systems seem to use the password credential class,
237 # if no credential class is specified we use password.
238 $config->{credential}{class} ||= '+Catalyst::Plugin::Authentication::Credential::Password';
240 my $credentialclass = $config->{'credential'}{'class'};
242 ## follow catalyst class naming - a + prefix means a fully qualified class, otherwise it's
243 ## taken to mean C::P::A::Credential::(specifiedclass)
244 if ($credentialclass !~ /^\+(.*)$/ ) {
245 $credentialclass = "Catalyst::Plugin::Authentication::Credential::${credentialclass}";
247 $credentialclass = $1;
250 # if we made it here - we have what we need to load the classes;
251 Catalyst::Utils::ensure_class_loaded( $credentialclass );
252 Catalyst::Utils::ensure_class_loaded( $storeclass );
254 # BACKWARDS COMPATIBILITY - if the store class does not define find_user, we define it in terms
255 # of get_user and add it to the class. this is because the auth routines use find_user,
256 # and rely on it being present. (this avoids per-call checks)
257 if (!$storeclass->can('find_user')) {
259 *{"${storeclass}::find_user"} = sub {
260 my ($self, $info) = @_;
261 my @rest = @{$info->{rest}} if exists($info->{rest});
262 $self->get_user($info->{id}, @rest);
266 ## a little cruft to stay compatible with some poorly written stores / credentials
267 ## we'll remove this soon.
268 if ($storeclass->can('new')) {
269 $app->auth_realms->{$realmname}{'store'} = $storeclass->new($config->{'store'}, $app);
271 $app->log->error("THIS IS DEPRECATED: $storeclass has no new() method - Attempting to use uninstantiated");
272 $app->auth_realms->{$realmname}{'store'} = $storeclass;
274 if ($credentialclass->can('new')) {
275 $app->auth_realms->{$realmname}{'credential'} = $credentialclass->new($config->{'credential'}, $app);
277 $app->log->error("THIS IS DEPRECATED: $credentialclass has no new() method - Attempting to use uninstantiated");
278 $app->auth_realms->{$realmname}{'credential'} = $credentialclass;
284 return($self->_auth_realms);
288 my ($app, $realmname) = @_;
289 return $app->auth_realms->{$realmname};
293 # Very internal method. Vital Valuable Urgent, Do not touch on pain of death.
294 # Using this method just assigns the default realm to be the value associated
295 # with the realmname provided. It WILL overwrite any real realm called 'default'
296 # so can be very confusing if used improperly. It's used properly already.
297 # Translation: don't use it.
298 sub _set_default_auth_realm {
299 my ($app, $realmname) = @_;
301 if (exists($app->auth_realms->{$realmname})) {
302 $app->auth_realms->{'default'} = $app->auth_realms->{$realmname};
304 return $app->get_auth_realm('default');
308 my ($app, $userinfo, $realmname) = @_;
311 $realmname = 'default';
314 my $realm = $app->get_auth_realm($realmname);
316 ## note to self - make authenticate throw an exception if realm is invalid.
318 if ($realm && exists($realm->{'credential'})) {
319 my $user = $realm->{'credential'}->authenticate($app, $realm->{store}, $userinfo);
321 $app->set_authenticated($user, $realmname);
325 $app->log->debug("The realm requested, '$realmname' does not exist," .
326 " or there is no credential associated with it.")
331 ## BACKWARDS COMPATIBILITY -- Warning: Here be monsters!
333 # What follows are backwards compatibility routines - for use with Stores and Credentials
334 # that have not been updated to work with C::P::Authentication v0.10.
335 # These are here so as to not break people's existing installations, but will go away
336 # in a future version.
338 # The old style of configuration only supports a single store, as each store module
339 # sets itself as the default store upon being loaded. This is the only supported
340 # 'compatibility' mode.
344 my ( $c, $uid, @rest ) = @_;
346 return $c->find_user( {'id' => $uid, 'rest'=>\@rest }, 'default' );
350 ## this should only be called when using old-style authentication plugins. IF this gets
351 ## called in a new-style config - it will OVERWRITE the store of your default realm. Don't do it.
352 ## also - this is a partial setup - because no credential is instantiated... in other words it ONLY
353 ## works with old-style auth plugins and C::P::Authentication in compatibility mode. Trying to combine
354 ## this with a realm-type config will probably crash your app.
355 sub default_auth_store {
358 if ( my $new = shift ) {
359 $self->auth_realms->{'default'}{'store'} = $new;
363 $storeclass = ref($new);
368 # BACKWARDS COMPATIBILITY - if the store class does not define find_user, we define it in terms
369 # of get_user and add it to the class. this is because the auth routines use find_user,
370 # and rely on it being present. (this avoids per-call checks)
371 if (!$storeclass->can('find_user')) {
373 *{"${storeclass}::find_user"} = sub {
374 my ($self, $info) = @_;
375 my @rest = @{$info->{rest}} if exists($info->{rest});
376 $self->get_user($info->{id}, @rest);
381 return $self->get_auth_realm('default')->{'store'};
384 ## BACKWARDS COMPATIBILITY
385 ## this only ever returns a hash containing 'default' - as that is the only
386 ## supported mode of calling this.
387 sub auth_store_names {
390 my %hash = ( $self->get_auth_realm('default')->{'store'} => 'default' );
394 my ( $self, $name ) = @_;
396 if ($name ne 'default') {
397 Carp::croak "get_auth_store called on non-default realm '$name'. Only default supported in compatibility mode";
399 $self->default_auth_store();
403 sub get_auth_store_name {
404 my ( $self, $store ) = @_;
408 # sub auth_stores is only used internally - here for completeness
412 my %hash = ( 'default' => $self->get_auth_realm('default')->{'store'});
423 Catalyst::Plugin::Authentication - Infrastructure plugin for the Catalyst
424 authentication framework.
433 $c->authenticate({ username => 'myusername',
434 password => 'mypassword' });
435 my $age = $c->user->get('age');
440 The authentication plugin provides generic user support for Catalyst apps. It
441 is the basis for both authentication (checking the user is who they claim to
442 be), and authorization (allowing the user to do what the system authorises
445 Using authentication is split into two parts. A Store is used to actually
446 store the user information, and can store any amount of data related to the
447 user. Credentials are used to verify users, using information from the store,
448 given data from the frontend. A Credential and a Store are paired to form a
449 'Realm'. A Catalyst application using the authentication framework must have
450 at least one realm, and may have several.
452 To implement authentication in a Catalyst application you need to add this
453 module, and specify at least one realm in the configuration.
455 Authentication data can also be stored in a session, if the application
456 is using the L<Catalyst::Plugin::Session> module.
458 B<NOTE> in version 0.10 of this module, the interface to this module changed.
459 Please see L</COMPATIBILITY ROUTINES> for more information.
463 =head2 The Authentication/Authorization Process
465 Web applications typically need to identify a user - to tell the user apart
466 from other users. This is usually done in order to display private information
467 that is only that user's business, or to limit access to the application so
468 that only certain entities can access certain parts.
470 This process is split up into several steps. First you ask the user to identify
471 themselves. At this point you can't be sure that the user is really who they
474 Then the user tells you who they are, and backs this claim with some piece of
475 information that only the real user could give you. For example, a password is
476 a secret that is known to both the user and you. When the user tells you this
477 password you can assume they're in on the secret and can be trusted (ignore
478 identity theft for now). Checking the password, or any other proof is called
479 B<credential verification>.
481 By this time you know exactly who the user is - the user's identity is
482 B<authenticated>. This is where this module's job stops, and your application
483 or other plugins step in.
485 The next logical step is B<authorization>, the process of deciding what a user
486 is (or isn't) allowed to do. For example, say your users are split into two
487 main groups - regular users and administrators. You want to verify that the
488 currently logged in user is indeed an administrator before performing the
489 actions in an administrative part of your application. These decisions may be
490 made within your application code using just the information available after
491 authentication, or it may be facilitated by a number of plugins.
493 =head2 The Components In This Framework
497 Configuration of the Catalyst::Plugin::Authentication framework is done in
498 terms of realms. In simplest terms, a realm is a pairing of a Credential
499 verifier and a User storage (Store) backend.
501 An application can have any number of Realms, each of which operates
502 independant of the others. Each realm has a name, which is used to identify it
503 as the target of an authentication request. This name can be anything, such as
504 'users' or 'members'. One realm must be defined as the default_realm, which is
505 used when no realm name is specified. More information about configuring
506 realms is available in the configuration section.
508 =head3 Credential Verifiers
510 When user input is transferred to the L<Catalyst> application (typically via
511 form inputs) the application may pass this information into the authentication
512 system through the $c->authenticate() method. From there, it is passed to the
513 appropriate Credential verifier.
515 These plugins check the data, and ensure that it really proves the user is who
518 =head3 Storage Backends
520 The authentication data also identifies a user, and the Storage backend modules
521 use this data to locate and return a standardized object-oriented
522 representation of a user.
524 When a user is retrieved from a store it is not necessarily authenticated.
525 Credential verifiers accept a set of authentication data and use this
526 information to retrieve the user from the store they are paired with.
528 =head3 The Core Plugin
530 This plugin on its own is the glue, providing realm configuration, session
531 integration, and other goodness for the other plugins.
535 More layers of plugins can be stacked on top of the authentication code. For
536 example, L<Catalyst::Plugin::Session::PerUser> provides an abstraction of
537 browser sessions that is more persistent per users.
538 L<Catalyst::Plugin::Authorization::Roles> provides an accepted way to separate
539 and group users into categories, and then check which categories the current
544 Let's say we were storing users in a simple perl hash. Users are
545 verified by supplying a password which is matched within the hash.
547 This means that our application will begin like this:
555 __PACKAGE__->config->{authentication} =
557 default_realm => 'members',
562 password_field => 'password',
563 password_type => 'clear'
569 password => "s00p3r",
571 roles => [qw/edit delete/],
574 password => "s3cr3t",
575 roles => [qw/comment/],
584 This tells the authentication plugin what realms are available, which
585 credential and store modules are used, and the configuration of each. With
586 this code loaded, we can now attempt to authenticate users.
588 To show an example of this, let's create an authentication controller:
590 package MyApp::Controller::Auth;
593 my ( $self, $c ) = @_;
595 if ( my $user = $c->req->param("user")
596 and my $password = $c->req->param("password") )
598 if ( $c->authenticate( { username => $user,
599 password => $password } ) ) {
600 $c->res->body( "hello " . $c->user->get("name") );
610 This code should be very readable. If all the necessary fields are supplied,
611 call the "authenticate" method from the controller. If it succeeds the
614 The credential verifier will attempt to retrieve the user whose details match
615 the authentication information provided to $c->authenticate(). Once it fetches
616 the user the password is checked and if it matches the user will be
617 B<authenticated> and C<< $c->user >> will contain the user object retrieved
620 In the above case, the default realm is checked, but we could just as easily
621 check an alternate realm. If this were an admin login, for example, we could
622 authenticate on the admin realm by simply changing the $c->authenticate()
625 if ( $c->authenticate( { username => $user,
626 password => $password }, 'admin' )l ) {
627 $c->res->body( "hello " . $c->user->get("name") );
631 Now suppose we want to restrict the ability to edit to a user with an
632 'editor' value of yes.
634 The restricted action might look like this:
637 my ( $self, $c ) = @_;
639 $c->detach("unauthorized")
640 unless $c->user_exists
641 and $c->user->get('editor') eq 'yes';
643 # do something restricted here
646 (Note that if you have multiple realms, you can use $c->user_in_realm('realmname')
647 in place of $c->user_exists(); This will essentially perform the same
648 verification as user_exists, with the added requirement that if there is a
649 user, it must have come from the realm specified.)
651 The above example is somewhat similar to role based access control.
652 L<Catalyst::Plugin::Authentication::Store::Minimal> treats the roles field as
653 an array of role names. Let's leverage this. Add the role authorization
662 my ( $self, $c ) = @_;
664 $c->detach("unauthorized") unless $c->check_roles("edit");
666 # do something restricted here
669 This is somewhat simpler and will work if you change your store, too, since the
670 role interface is consistent.
672 Let's say your app grew, and you now have 10000 users. It's no longer
673 efficient to maintain a hash of users, so you move this data to a database.
674 You can accomplish this simply by installing the DBIx::Class Store and
675 changing your config:
677 __PACKAGE__->config->{authentication} =
679 default_realm => 'members',
684 password_field => 'password',
685 password_type => 'clear'
688 class => 'DBIx::Class',
689 user_class => 'MyApp::Users',
690 role_column => 'roles'
696 The authentication system works behind the scenes to load your data from the
697 new source. The rest of your application is completely unchanged.
705 __PACKAGE__->config->{authentication} =
707 default_realm => 'members',
712 password_field => 'password',
713 password_type => 'clear'
716 class => 'DBIx::Class',
717 user_class => 'MyApp::Users',
718 role_column => 'roles'
724 password_field => 'password',
725 password_type => 'clear'
728 class => '+MyApp::Authentication::Store::NetAuth',
729 authserver => '192.168.10.17'
738 Whether or not to store the user's logged in state in the session, if the
739 application is also using L<Catalyst::Plugin::Session>. This
740 value is set to true per default.
744 This defines which realm should be used as when no realm is provided to methods
745 that require a realm such as authenticate or find_user.
749 This contains the series of realm configurations you want to use for your app.
750 The only rule here is that there must be at least one. A realm consists of a
751 name, which is used to reference the realm, a credential and a store.
753 Each realm config contains two hashes, one called 'credential' and one called
754 'store', each of which provide configuration details to the respective modules.
755 The contents of these hashes is specific to the module being used, with the
756 exception of the 'class' element, which tells the core Authentication module the
757 classname to instantiate.
759 The 'class' element follows the standard Catalyst mechanism of class
760 specification. If a class is prefixed with a +, it is assumed to be a complete
761 class name. Otherwise it is considered to be a portion of the class name. For
762 credentials, the classname 'B<Password>', for example, is expanded to
763 Catalyst::Plugin::Authentication::Credential::B<Password>. For stores, the
764 classname 'B<storename>' is expanded to:
765 Catalyst::Plugin::Authentication::Store::B<storename>.
775 =item authenticate( $userinfo, $realm )
777 Attempts to authenticate the user using the information in the $userinfo hash
778 reference using the realm $realm. $realm may be omitted, in which case the
779 default realm is checked.
783 Returns the currently logged in user or undef if there is none.
787 Returns true if a user is logged in right now. The difference between
788 user_exists and user is that user_exists will return true if a user is logged
789 in, even if it has not been yet retrieved from the storage backend. If you only
790 need to know if the user is logged in, depending on the storage mechanism this
791 can be much more efficient.
793 =item user_in_realm ( $realm )
795 Works like user_exists, except that it only returns true if a user is both
796 logged in right now and was retrieved from the realm provided.
800 Logs the user out, Deletes the currently logged in user from $c->user and the session.
802 =item find_user( $userinfo, $realm )
804 Fetch a particular users details, matching the provided user info, from the realm
809 =head1 INTERNAL METHODS
811 These methods are for Catalyst::Plugin::Authentication B<INTERNAL USE> only.
812 Please do not use them in your own code, whether application or credential /
813 store modules. If you do, you will very likely get the nasty shock of having
814 to fix / rewrite your code when things change. They are documented here only
819 =item set_authenticated ( $user, $realmname )
821 Marks a user as authenticated. This is called from within the authenticate
822 routine when a credential returns a user. $realmname defaults to 'default'
824 =item auth_restore_user ( $user, $realmname )
826 Used to restore a user from the session. In most cases this is called without
827 arguments to restore the user via the session. Can be called with arguments
828 when restoring a user from some other method. Currently not used in this way.
830 =item save_user_in_session ( $user, $realmname )
832 Used to save the user in a session. Saves $user in session, marked as
833 originating in $realmname. Both arguments are required.
837 Returns a hashref containing realmname -> realm instance pairs. Realm
838 instances contain an instantiated store and credential object as the 'store'
839 and 'credential' elements, respectively
841 =item get_auth_realm ( $realmname )
843 Retrieves the realm instance for the realmname provided.
851 This list might not be up to date. Below are modules known to work with the updated
852 API of 0.10 and are therefore compatible with realms.
854 =head2 User Storage Backends
856 L<Catalyst::Plugin::Authentication::Store::Minimal>,
857 L<Catalyst::Plugin::Authentication::Store::DBIx::Class>,
859 =head2 Credential verification
861 L<Catalyst::Plugin::Authentication::Credential::Password>,
865 L<Catalyst::Plugin::Authorization::ACL>,
866 L<Catalyst::Plugin::Authorization::Roles>
868 =head2 Internals Documentation
870 L<Catalyst::Plugin::Authentication::Internals>
874 L<Catalyst::Plugin::Session>,
875 L<Catalyst::Plugin::Session::PerUser>
877 =head1 DON'T SEE ALSO
879 This module along with its sub plugins deprecate a great number of other
880 modules. These include L<Catalyst::Plugin::Authentication::Simple>,
881 L<Catalyst::Plugin::Authentication::CDBI>.
883 At the time of writing these plugins have not yet been replaced or updated, but
884 should be eventually: L<Catalyst::Plugin::Authentication::OpenID>,
885 L<Catalyst::Plugin::Authentication::LDAP>,
886 L<Catalyst::Plugin::Authentication::CDBI::Basic>,
887 L<Catalyst::Plugin::Authentication::Basic::Remote>.
889 =head1 INCOMPATABILITIES
891 The realms based configuration and functionality of the 0.10 update
892 of L<Catalyst::Plugin::Authentication> required a change in the API used by
893 credentials and stores. It has a compatibility mode which allows use of
894 modules that have not yet been updated. This, however, completely mimics the
895 older api and disables the new realm-based features. In other words you can
896 not mix the older credential and store modules with realms, or realm-based
897 configs. The changes required to update modules are relatively minor and are
898 covered in L<Catalyst::Plugin::Authentication::Internals>. We hope that most
899 modules will move to the compatible list above very quickly.
901 =head1 COMPATIBILITY ROUTINES
903 In version 0.10 of L<Catalyst::Plugin::Authentication>, the API
904 changed. For app developers, this change is fairly minor, but for
905 Credential and Store authors, the changes are significant.
907 Please see the documentation in version 0.09 of
908 Catalyst::Plugin::Authentication for a better understanding of how the old API
911 The items below are still present in the plugin, though using them is
912 deprecated. They remain only as a transition tool, for those sites which can
913 not yet be upgraded to use the new system due to local customizations or use
914 of Credential / Store modules that have not yet been updated to work with the
917 These routines should not be used in any application using realms
918 functionality or any of the methods described above. These are for reference
925 This method is used to initiate authentication and user retrieval. Technically
926 this is part of the old Password credential module and it still resides in the
927 L<Password|Catalyst::Plugin::Authentication::Credential::Password> class. It is
928 included here for reference only.
930 =item default_auth_store
932 Return the store whose name is 'default'.
934 This is set to C<< $c->config->{authentication}{store} >> if that value exists,
935 or by using a Store plugin:
937 # load the Minimal authentication store.
938 use Catalyst qw/Authentication Authentication::Store::Minimal/;
940 Sets the default store to
941 L<Catalyst::Plugin::Authentication::Store::Minimal>.
943 =item get_auth_store $name
945 Return the store whose name is $name.
947 =item get_auth_store_name $store
949 Return the name of the store $store.
953 A hash keyed by name, with the stores registered in the app.
955 =item register_auth_stores %stores_by_name
957 Register stores into the application.
965 Yuval Kogman, C<nothingmuch@woobling.org>
967 Jay Kuri, C<jayk@cpan.org>
974 =head1 COPYRIGHT & LICENSE
976 Copyright (c) 2005 the aforementioned authors. All rights
977 reserved. This program is free software; you can redistribute
978 it and/or modify it under the same terms as Perl itself.