1 package Catalyst::Plugin::Authentication;
3 use base qw/Class::Accessor::Fast Class::Data::Inheritable/;
5 __PACKAGE__->mk_accessors(qw/_user/);
13 use Catalyst::Authentication::Realm;
15 our $VERSION = "0.10013";
17 sub set_authenticated {
18 my ( $c, $user, $realmname ) = @_;
21 $c->request->{user} = $user; # compatibility kludge
24 $realmname = 'default';
26 my $realm = $c->get_auth_realm($realmname);
29 Catalyst::Exception->throw(
30 "set_authenticated called with nonexistant realm: '$realmname'.");
32 $user->auth_realm($realm->name);
36 $c->maybe::next::method($user, $realmname);
46 if ( defined($c->_user) ) {
49 return $c->auth_restore_user;
53 # change this to allow specification of a realm - to verify the user is part of that realm
54 # in addition to verifying that they exist.
57 return defined($c->_user) || defined($c->find_realm_for_persisted_user);
60 # works like user_exists - except only returns true if user
61 # exists AND is in the realm requested.
63 my ($c, $realmname) = @_;
65 if (defined($c->_user)) {
66 return ($c->_user->auth_realm eq $realmname);
68 my $realm = $c->find_realm_for_persisted_user;
70 return ($realm->name eq $realmname);
77 sub __old_save_user_in_session {
78 my ( $c, $user, $realmname ) = @_;
80 $c->session->{__user_realm} = $realmname;
82 # we want to ask the store for a user prepared for the session.
83 # but older modules split this functionality between the user and the
84 # store. We try the store first. If not, we use the old method.
85 my $realm = $c->get_auth_realm($realmname);
86 if ($realm->{'store'}->can('for_session')) {
87 $c->session->{__user} = $realm->{'store'}->for_session($c, $user);
89 $c->session->{__user} = $user->for_session;
96 if ($c->user_exists) {
98 ## if we have a valid session handler - we store the
99 ## realm in the session. If not - we have to hope that
100 ## the realm can recognize its frozen user somehow.
101 if ($c->can('session') &&
102 $c->config->{'Plugin::Authentication'}{'use_session'} &&
103 $c->session_is_valid) {
105 $c->session->{'__user_realm'} = $c->_user->auth_realm;
108 my $realm = $c->get_auth_realm($c->_user->auth_realm);
110 # used to call $realm->save_user_in_session
111 $realm->persist_user($c, $c->user);
116 ## this was a short lived method to update user information -
117 ## you should use persist_user instead.
118 sub update_user_in_session {
121 return $c->persist_user;
129 my $realm = $c->find_realm_for_persisted_user;
131 $realm->remove_persisted_user($c);
134 $c->maybe::next::method(@_);
138 my ( $c, $userinfo, $realmname ) = @_;
140 $realmname ||= 'default';
141 my $realm = $c->get_auth_realm($realmname);
144 Catalyst::Exception->throw(
145 "find_user called with nonexistant realm: '$realmname'.");
147 return $realm->find_user($userinfo, $c);
150 ## Consider making this a public method. - would make certain things easier when
151 ## dealing with things pre-auth restore.
152 sub find_realm_for_persisted_user {
156 if ($c->can('session')
157 and $c->config->{'Plugin::Authentication'}{'use_session'}
158 and $c->session_is_valid
159 and exists($c->session->{'__user_realm'})) {
161 $realm = $c->auth_realms->{$c->session->{'__user_realm'}};
162 if ($realm->user_is_restorable($c)) {
166 ## we have no choice but to ask each realm whether it has a persisted user.
167 foreach my $realmname (@{$c->_auth_realm_restore_order}) {
168 my $realm = $c->auth_realms->{$realmname}
169 || Catalyst::Exception->throw("Could not find authentication realm '$realmname'");
171 if $realm->user_is_restorable($c);
177 sub auth_restore_user {
178 my ( $c, $frozen_user, $realmname ) = @_;
181 if (defined($realmname)) {
182 $realm = $c->get_auth_realm($realmname);
184 $realm = $c->find_realm_for_persisted_user;
186 return undef unless $realm; # FIXME die unless? This is an internal inconsistency
188 $c->_user( my $user = $realm->restore_user( $c, $frozen_user ) );
190 # this sets the realm the user originated in.
191 $user->auth_realm($realm->name) if $user;
197 # we can't actually do our setup in setup because the model has not yet been loaded.
198 # So we have to trigger off of setup_finished. :-(
202 $app->_authentication_initialize();
203 $app->next::method(@_);
206 ## the actual initialization routine. whee.
207 sub _authentication_initialize {
210 ## let's avoid recreating / configuring everything if we have already done it, eh?
211 if ($app->can('_auth_realms')) { return };
213 ## make classdata where it is used.
214 $app->mk_classdata( '_auth_realms' => {});
216 ## the order to attempt restore in - If we don't have session - we have
217 ## no way to be sure where a frozen user came from - so we have to
218 ## ask each realm if it can restore the user. Unfortunately it is possible
219 ## that multiple realms could restore the user from the data we have -
220 ## So we have to determine at setup time what order to ask the realms in.
221 ## The default is to use the user_restore_priority values defined in the realm
222 ## config. if they are not defined - we go by alphabetical order. Note that
223 ## the 'default' realm always gets first chance at it unless it is explicitly
224 ## placed elsewhere by user_restore_priority. Remember this only comes
225 ## into play if session is disabled.
227 $app->mk_classdata( '_auth_realm_restore_order' => []);
229 my $cfg = $app->config->{'Plugin::Authentication'};
231 if (!defined($cfg)) {
232 if (exists($app->config->{'authentication'})) {
233 $cfg = $app->config->{'authentication'};
234 $app->config->{'Plugin::Authentication'} = $app->config->{'authentication'};
239 # the realmshash contains the various configured realms. By default this is
240 # the main $app->config->{'Plugin::Authentication'} hash - but if that is
241 # not defined, or there is a subkey {'realms'} then we use that.
245 ## If we have a sub-key of {'realms'} then we use that for realm configuration
246 if (exists($cfg->{'realms'})) {
247 $realmshash = $cfg->{'realms'};
250 # old default was to force use_session on. This must remain for that
251 # reason - but if use_session is already in the config, we respect its setting.
252 if (!exists($cfg->{'use_session'})) {
253 $cfg->{'use_session'} = 1;
256 ## if we have a realms hash
257 if (ref($realmshash) eq 'HASH') {
259 my %auth_restore_order;
261 my $defaultrealm = 'default';
263 foreach my $realm (sort keys %{$realmshash}) {
264 if (ref($realmshash->{$realm}) eq 'HASH' &&
265 (exists($realmshash->{$realm}{credential}) || exists($realmshash->{$realm}{class}))) {
267 $app->setup_auth_realm($realm, $realmshash->{$realm});
269 if (exists($realmshash->{$realm}{'user_restore_priority'})) {
270 $auth_restore_order{$realm} = $realmshash->{$realm}{'user_restore_priority'};
272 $auth_restore_order{$realm} = $authcount++;
277 # if we have a 'default_realm' in the config hash and we don't already
278 # have a realm called 'default', we point default at the realm specified
279 if (exists($cfg->{'default_realm'}) && !$app->get_auth_realm('default')) {
280 if ($app->_set_default_auth_realm($cfg->{'default_realm'})) {
281 $defaultrealm = $cfg->{'default_realm'};
282 $auth_restore_order{'default'} = $auth_restore_order{$cfg->{'default_realm'}};
283 delete($auth_restore_order{$cfg->{'default_realm'}});
287 ## if the default realm did not have a defined priority in its config - we put it at the front.
288 if (!exists($realmshash->{$defaultrealm}{'user_restore_priority'})) {
289 $auth_restore_order{'default'} = 1;
292 @{$app->_auth_realm_restore_order} = sort { $auth_restore_order{$a} <=> $auth_restore_order{$b} } keys %auth_restore_order;
296 ## BACKWARDS COMPATIBILITY - if realms is not defined - then we are probably dealing
297 ## with an old-school config. The only caveat here is that we must add a classname
299 ## also - we have to treat {store} as {stores}{default} - because
300 ## while it is not a clear as a valid config in the docs, it
301 ## is functional with the old api. Whee!
302 if (exists($cfg->{'store'}) && !exists($cfg->{'stores'}{'default'})) {
303 $cfg->{'stores'}{'default'} = $cfg->{'store'};
306 push @{$app->_auth_realm_restore_order}, 'default';
307 foreach my $storename (keys %{$cfg->{'stores'}}) {
309 store => { class => $cfg->{'stores'}{$storename} },
311 print STDERR "Foo, ok?\n";
312 $app->setup_auth_realm($storename, $realmcfg);
319 sub setup_auth_realm {
320 my ($app, $realmname, $config) = @_;
322 my $realmclass = $config->{class};
325 $realmclass = 'Catalyst::Authentication::Realm';
326 } elsif ($realmclass !~ /^\+(.*)$/ ) {
327 $realmclass = "Catalyst::Authentication::Realm::${realmclass}";
332 Catalyst::Utils::ensure_class_loaded( $realmclass );
334 my $realm = $realmclass->new($realmname, $config, $app);
336 $app->auth_realms->{$realmname} = $realm;
338 $app->log->debug("realm initialization for '$realmname' failed.");
345 return($self->_auth_realms);
349 my ($app, $realmname) = @_;
351 return $app->auth_realms->{$realmname};
356 # Very internal method. Vital Valuable Urgent, Do not touch on pain of death.
357 # Using this method just assigns the default realm to be the value associated
358 # with the realmname provided. It WILL overwrite any real realm called 'default'
359 # so can be very confusing if used improperly. It's used properly already.
360 # Translation: don't use it.
361 sub _set_default_auth_realm {
362 my ($app, $realmname) = @_;
364 if (exists($app->auth_realms->{$realmname})) {
365 $app->auth_realms->{'default'} = $app->auth_realms->{$realmname};
367 return $app->get_auth_realm('default');
371 my ($app, $userinfo, $realmname) = @_;
374 $realmname = 'default';
377 my $realm = $app->get_auth_realm($realmname);
379 ## note to self - make authenticate throw an exception if realm is invalid.
382 return $realm->authenticate($app, $userinfo);
384 Catalyst::Exception->throw(
385 "authenticate called with nonexistant realm: '$realmname'.");
391 ## BACKWARDS COMPATIBILITY -- Warning: Here be monsters!
393 # What follows are backwards compatibility routines - for use with Stores and Credentials
394 # that have not been updated to work with C::P::Authentication v0.10.
395 # These are here so as to not break people's existing installations, but will go away
396 # in a future version.
398 # The old style of configuration only supports a single store, as each store module
399 # sets itself as the default store upon being loaded. This is the only supported
400 # 'compatibility' mode.
404 my ( $c, $uid, @rest ) = @_;
406 return $c->find_user( {'id' => $uid, 'rest'=>\@rest }, 'default' );
410 ## this should only be called when using old-style authentication plugins. IF this gets
411 ## called in a new-style config - it will OVERWRITE the store of your default realm. Don't do it.
412 ## also - this is a partial setup - because no credential is instantiated... in other words it ONLY
413 ## works with old-style auth plugins and C::P::Authentication in compatibility mode. Trying to combine
414 ## this with a realm-type config will probably crash your app.
415 sub default_auth_store {
418 my $realm = $self->get_auth_realm('default');
420 $realm = $self->setup_auth_realm('default', { class => 'Compatibility' });
422 if ( my $new = shift ) {
427 $storeclass = ref($new);
432 # BACKWARDS COMPATIBILITY - if the store class does not define find_user, we define it in terms
433 # of get_user and add it to the class. this is because the auth routines use find_user,
434 # and rely on it being present. (this avoids per-call checks)
435 if (!$storeclass->can('find_user')) {
437 *{"${storeclass}::find_user"} = sub {
438 my ($self, $info) = @_;
439 my @rest = @{$info->{rest}} if exists($info->{rest});
440 $self->get_user($info->{id}, @rest);
445 return $self->get_auth_realm('default')->store;
448 ## BACKWARDS COMPATIBILITY
449 ## this only ever returns a hash containing 'default' - as that is the only
450 ## supported mode of calling this.
451 sub auth_store_names {
454 my %hash = ( $self->get_auth_realm('default')->store => 'default' );
458 my ( $self, $name ) = @_;
460 if ($name ne 'default') {
461 Carp::croak "get_auth_store called on non-default realm '$name'. Only default supported in compatibility mode";
463 $self->default_auth_store();
467 sub get_auth_store_name {
468 my ( $self, $store ) = @_;
472 # sub auth_stores is only used internally - here for completeness
476 my %hash = ( 'default' => $self->get_auth_realm('default')->store);
487 Catalyst::Plugin::Authentication - Infrastructure plugin for the Catalyst
488 authentication framework.
497 $c->authenticate({ username => 'myusername',
498 password => 'mypassword' });
499 my $age = $c->user->get('age');
504 The authentication plugin provides generic user support for Catalyst apps. It
505 is the basis for both authentication (checking the user is who they claim to
506 be), and authorization (allowing the user to do what the system authorises
509 Using authentication is split into two parts. A Store is used to actually
510 store the user information, and can store any amount of data related to the
511 user. Credentials are used to verify users, using information from the store,
512 given data from the frontend. A Credential and a Store are paired to form a
513 'Realm'. A Catalyst application using the authentication framework must have
514 at least one realm, and may have several.
516 To implement authentication in a Catalyst application you need to add this
517 module, and specify at least one realm in the configuration.
519 Authentication data can also be stored in a session, if the application
520 is using the L<Catalyst::Plugin::Session> module.
522 B<NOTE> in version 0.10 of this module, the interface to this module changed.
523 Please see L</COMPATIBILITY ROUTINES> for more information.
527 =head2 The Authentication/Authorization Process
529 Web applications typically need to identify a user - to tell the user apart
530 from other users. This is usually done in order to display private information
531 that is only that user's business, or to limit access to the application so
532 that only certain entities can access certain parts.
534 This process is split up into several steps. First you ask the user to identify
535 themselves. At this point you can't be sure that the user is really who they
538 Then the user tells you who they are, and backs this claim with some piece of
539 information that only the real user could give you. For example, a password is
540 a secret that is known to both the user and you. When the user tells you this
541 password you can assume they're in on the secret and can be trusted (ignore
542 identity theft for now). Checking the password, or any other proof is called
543 B<credential verification>.
545 By this time you know exactly who the user is - the user's identity is
546 B<authenticated>. This is where this module's job stops, and your application
547 or other plugins step in.
549 The next logical step is B<authorization>, the process of deciding what a user
550 is (or isn't) allowed to do. For example, say your users are split into two
551 main groups - regular users and administrators. You want to verify that the
552 currently logged in user is indeed an administrator before performing the
553 actions in an administrative part of your application. These decisions may be
554 made within your application code using just the information available after
555 authentication, or it may be facilitated by a number of plugins.
557 =head2 The Components In This Framework
561 Configuration of the Catalyst::Plugin::Authentication framework is done in
562 terms of realms. In simplest terms, a realm is a pairing of a Credential
563 verifier and a User storage (Store) backend. As of version 0.10003, realms are
564 now objects that you can create and customize.
566 An application can have any number of Realms, each of which operates
567 independent of the others. Each realm has a name, which is used to identify it
568 as the target of an authentication request. This name can be anything, such as
569 'users' or 'members'. One realm must be defined as the default_realm, which is
570 used when no realm name is specified. More information about configuring
571 realms is available in the configuration section.
573 =head3 Credential Verifiers
575 When user input is transferred to the L<Catalyst> application
576 (typically via form inputs) the application may pass this information
577 into the authentication system through the C<< $c->authenticate() >>
578 method. From there, it is passed to the appropriate Credential
581 These plugins check the data, and ensure that it really proves the user is who
584 Credential verifiers compatible with versions of this module 0.10x and
585 upwards should be in the namespace
586 C<Catalyst::Authentication::Credential>.
588 =head3 Storage Backends
590 The authentication data also identifies a user, and the Storage backend modules
591 use this data to locate and return a standardized object-oriented
592 representation of a user.
594 When a user is retrieved from a store it is not necessarily authenticated.
595 Credential verifiers accept a set of authentication data and use this
596 information to retrieve the user from the store they are paired with.
598 Storage backends compatible with versions of this module 0.10x and
599 upwards should be in the namespace
600 C<Catalyst::Authentication::Store>.
602 =head3 The Core Plugin
604 This plugin on its own is the glue, providing realm configuration, session
605 integration, and other goodness for the other plugins.
609 More layers of plugins can be stacked on top of the authentication code. For
610 example, L<Catalyst::Plugin::Session::PerUser> provides an abstraction of
611 browser sessions that is more persistent per user.
612 L<Catalyst::Plugin::Authorization::Roles> provides an accepted way to separate
613 and group users into categories, and then check which categories the current
618 Let's say we were storing users in a simple Perl hash. Users are
619 verified by supplying a password which is matched within the hash.
621 This means that our application will begin like this:
629 __PACKAGE__->config( 'Plugin::Authentication' =>
634 password_field => 'password',
635 password_type => 'clear'
641 password => "s00p3r",
643 roles => [qw/edit delete/],
646 password => "s3cr3t",
647 roles => [qw/comment/],
655 This tells the authentication plugin what realms are available, which
656 credential and store modules are used, and the configuration of each. With
657 this code loaded, we can now attempt to authenticate users.
659 To show an example of this, let's create an authentication controller:
661 package MyApp::Controller::Auth;
664 my ( $self, $c ) = @_;
666 if ( my $user = $c->req->params->{user}
667 and my $password = $c->req->params->{password} )
669 if ( $c->authenticate( { username => $user,
670 password => $password } ) ) {
671 $c->res->body( "hello " . $c->user->get("name") );
681 This code should be self-explanatory. If all the necessary fields are supplied,
682 call the C<authenticate> method on the context object. If it succeeds the
685 The credential verifier will attempt to retrieve the user whose
686 details match the authentication information provided to
687 C<< $c->authenticate() >>. Once it fetches the user the password is
688 checked and if it matches the user will be B<authenticated> and
689 C<< $c->user >> will contain the user object retrieved from the store.
691 In the above case, the default realm is checked, but we could just as easily
692 check an alternate realm. If this were an admin login, for example, we could
693 authenticate on the admin realm by simply changing the C<< $c->authenticate() >>
696 if ( $c->authenticate( { username => $user,
697 password => $password }, 'admin' ) ) {
698 $c->res->body( "hello " . $c->user->get("name") );
702 Now suppose we want to restrict the ability to edit to a user with an
703 'editor' value of yes.
705 The restricted action might look like this:
708 my ( $self, $c ) = @_;
710 $c->detach("unauthorized")
711 unless $c->user_exists
712 and $c->user->get('editor') eq 'yes';
714 # do something restricted here
717 (Note that if you have multiple realms, you can use
718 C<< $c->user_in_realm('realmname') >> in place of
719 C<< $c->user_exists(); >> This will essentially perform the same
720 verification as user_exists, with the added requirement that if there
721 is a user, it must have come from the realm specified.)
723 The above example is somewhat similar to role based access control.
724 L<Catalyst::Authentication::Store::Minimal> treats the roles field as
725 an array of role names. Let's leverage this. Add the role authorization
734 my ( $self, $c ) = @_;
736 $c->detach("unauthorized") unless $c->check_user_roles("edit");
738 # do something restricted here
741 This is somewhat simpler and will work if you change your store, too, since the
742 role interface is consistent.
744 Let's say your app grows, and you now have 10,000 users. It's no longer
745 efficient to maintain a hash of users, so you move this data to a database.
746 You can accomplish this simply by installing the L<DBIx::Class|Catalyst::Authentication::Store::DBIx::Class> Store and
747 changing your config:
749 __PACKAGE__->config( 'Plugin::Authentication'} =>
751 default_realm => 'members',
755 password_field => 'password',
756 password_type => 'clear'
759 class => 'DBIx::Class',
760 user_class => 'MyApp::Users',
761 role_column => 'roles'
767 The authentication system works behind the scenes to load your data from the
768 new source. The rest of your application is completely unchanged.
774 __PACKAGE__->config( 'Plugin::Authentication' =>
776 default_realm => 'members',
781 password_field => 'password',
782 password_type => 'clear'
785 class => 'DBIx::Class',
786 user_class => 'MyApp::Users',
787 role_column => 'roles'
793 password_field => 'password',
794 password_type => 'clear'
797 class => '+MyApp::Authentication::Store::NetAuth',
798 authserver => '192.168.10.17'
804 NOTE: Until version 0.10008 of this module, you would need to put all the
805 realms inside a "realms" key in the configuration. Please see
806 L</COMPATIBILITY CONFIGURATION> for more information
812 Whether or not to store the user's logged in state in the session, if the
813 application is also using L<Catalyst::Plugin::Session>. This
814 value is set to true per default.
816 However, even if use_session is disabled, if any code touches $c->session, a session
817 object will be auto-vivified and session Cookies will be sent in the headers. To
818 prevent accidental session creation, check if a session already exists with
819 if ($c->sessionid) { ... }. If the session doesn't exist, then don't place
820 anything in the session to prevent an unecessary session from being created.
824 This defines which realm should be used as when no realm is provided to methods
825 that require a realm such as authenticate or find_user.
829 The Plugin::Authentication config hash contains the series of realm
830 configurations you want to use for your app. The only rule here is
831 that there must be at least one. A realm consists of a name, which is used
832 to reference the realm, a credential and a store. You may also put your
833 realm configurations within a subelement called 'realms' if you desire to
834 separate them from the remainder of your configuration. Note that if you use
835 a 'realms' subelement, you must put ALL of your realms within it.
837 You can also specify a realm class to instantiate instead of the default
838 L<Catalyst::Authentication::Realm> class using the 'class' element within the
841 Each realm config contains two hashes, one called 'credential' and one called
842 'store', each of which provide configuration details to the respective modules.
843 The contents of these hashes is specific to the module being used, with the
844 exception of the 'class' element, which tells the core Authentication module the
845 classname to instantiate.
847 The 'class' element follows the standard Catalyst mechanism of class
848 specification. If a class is prefixed with a +, it is assumed to be a complete
849 class name. Otherwise it is considered to be a portion of the class name. For
850 credentials, the classname 'B<Password>', for example, is expanded to
851 Catalyst::Authentication::Credential::B<Password>. For stores, the
852 classname 'B<storename>' is expanded to:
853 Catalyst::Authentication::Store::B<storename>.
859 =head2 $c->authenticate( $userinfo [, $realm ])
861 Attempts to authenticate the user using the information in the $userinfo hash
862 reference using the realm $realm. $realm may be omitted, in which case the
863 default realm is checked.
867 Returns the currently logged in user, or undef if there is none.
869 =head2 $c->user_exists( )
871 Returns true if a user is logged in right now. The difference between
872 user_exists and user is that user_exists will return true if a user is logged
873 in, even if it has not been yet retrieved from the storage backend. If you only
874 need to know if the user is logged in, depending on the storage mechanism this
875 can be much more efficient.
877 =head2 $c->user_in_realm( $realm )
879 Works like user_exists, except that it only returns true if a user is both
880 logged in right now and was retrieved from the realm provided.
884 Logs the user out. Deletes the currently logged in user from C<< $c->user >> and the session.
886 =head2 $c->find_user( $userinfo, $realm )
888 Fetch a particular users details, matching the provided user info, from the realm
891 =head2 persist_user()
893 Under normal circumstances the user data is only saved to the session during
894 initial authentication. This call causes the auth system to save the
895 currently authenticated user's data across requests. Useful if you have
896 changed the user data and want to ensure that future requests reflect the
897 most current data. Assumes that at the time of this call, $c->user
898 contains the most current data.
900 =head2 find_realm_for_persisted_user()
902 Private method, do not call from user code!
904 =head1 INTERNAL METHODS
906 These methods are for Catalyst::Plugin::Authentication B<INTERNAL USE> only.
907 Please do not use them in your own code, whether application or credential /
908 store modules. If you do, you will very likely get the nasty shock of having
909 to fix / rewrite your code when things change. They are documented here only
912 =head2 $c->set_authenticated( $user, $realmname )
914 Marks a user as authenticated. This is called from within the authenticate
915 routine when a credential returns a user. $realmname defaults to 'default'
917 =head2 $c->auth_restore_user( $user, $realmname )
919 Used to restore a user from the session. In most cases this is called without
920 arguments to restore the user via the session. Can be called with arguments
921 when restoring a user from some other method. Currently not used in this way.
923 =head2 $c->auth_realms( )
925 Returns a hashref containing realmname -> realm instance pairs. Realm
926 instances contain an instantiated store and credential object as the 'store'
927 and 'credential' elements, respectively
929 =head2 $c->get_auth_realm( $realmname )
931 Retrieves the realm instance for the realmname provided.
933 =head2 $c->update_user_in_session
935 This was a short-lived method to update user information - you should use persist_user instead.
937 =head2 $c->setup_auth_realm( )
939 =head1 OVERRIDDEN METHODS
945 This list might not be up to date. Below are modules known to work with the updated
946 API of 0.10 and are therefore compatible with realms.
950 L<Catalyst::Authentication::Realm>
952 =head2 User Storage Backends
956 =item L<Catalyst::Authentication::Store::Minimal>
958 =item L<Catalyst::Authentication::Store::DBIx::Class>
960 =item L<Catalyst::Authentication::Store::LDAP>
962 =item L<Catalyst::Authentication::Store::RDBO>
964 =item L<Catalyst::Authentication::Store::Model::KiokuDB>
966 =item L<Catalyst::Authentication::Store::Jifty::DBI>
968 =item L<Catalyst::Authentication::Store::Htpasswd>
972 =head2 Credential verification
976 =item L<Catalyst::Authentication::Credential::Password>
978 =item L<Catalyst::Authentication::Credential::HTTP>
980 =item L<Catalyst::Authentication::Credential::OpenID>
982 =item L<Catalyst::Authentication::Credential::Authen::Simple>
984 =item L<Catalyst::Authentication::Credential::Flickr>
986 =item L<Catalyst::Authentication::Credential::Testing>
988 =item L<Catalyst::Authentication::Credential::AuthTkt>
990 =item L<Catalyst::Authentication::Credential::Kerberos>
996 L<Catalyst::Plugin::Authorization::ACL>,
997 L<Catalyst::Plugin::Authorization::Roles>
999 =head2 Internals Documentation
1001 L<Catalyst::Plugin::Authentication::Internals>
1005 L<Catalyst::Plugin::Session>,
1006 L<Catalyst::Plugin::Session::PerUser>
1008 =head1 DON'T SEE ALSO
1010 This module along with its sub plugins deprecate a great number of other
1011 modules. These include L<Catalyst::Plugin::Authentication::Simple>,
1012 L<Catalyst::Plugin::Authentication::CDBI>.
1014 =head1 INCOMPATABILITIES
1016 The realms-based configuration and functionality of the 0.10 update
1017 of L<Catalyst::Plugin::Authentication> required a change in the API used by
1018 credentials and stores. It has a compatibility mode which allows use of
1019 modules that have not yet been updated. This, however, completely mimics the
1020 older api and disables the new realm-based features. In other words you cannot
1021 mix the older credential and store modules with realms, or realm-based
1022 configs. The changes required to update modules are relatively minor and are
1023 covered in L<Catalyst::Plugin::Authentication::Internals>. We hope that most
1024 modules will move to the compatible list above very quickly.
1026 =head1 COMPATIBILITY CONFIGURATION
1028 Until version 0.10008 of this module, you needed to put all the
1029 realms inside a "realms" key in the configuration.
1032 __PACKAGE__->config( 'Plugin::Authentication'} =>
1034 default_realm => 'members',
1043 If you use the old, deprecated C<< __PACKAGE__->config( 'authentication' ) >>
1044 configuration key, then the realms key is still required.
1046 =head1 COMPATIBILITY ROUTINES
1048 In version 0.10 of L<Catalyst::Plugin::Authentication>, the API
1049 changed. For app developers, this change is fairly minor, but for
1050 Credential and Store authors, the changes are significant.
1052 Please see the documentation in version 0.09 of
1053 Catalyst::Plugin::Authentication for a better understanding of how the old API
1056 The items below are still present in the plugin, though using them is
1057 deprecated. They remain only as a transition tool, for those sites which can
1058 not yet be upgraded to use the new system due to local customizations or use
1059 of Credential / Store modules that have not yet been updated to work with the
1062 These routines should not be used in any application using realms
1063 functionality or any of the methods described above. These are for reference
1068 This method is used to initiate authentication and user retrieval. Technically
1069 this is part of the old Password credential module and it still resides in the
1070 L<Password|Catalyst::Plugin::Authentication::Credential::Password> class. It is
1071 included here for reference only.
1073 =head2 $c->default_auth_store( )
1075 Return the store whose name is 'default'.
1077 This is set to C<< $c->config( 'Plugin::Authentication' => { store => # Store} ) >> if that value exists,
1078 or by using a Store plugin:
1080 # load the Minimal authentication store.
1081 use Catalyst qw/Authentication Authentication::Store::Minimal/;
1083 Sets the default store to
1084 L<Catalyst::Plugin::Authentication::Store::Minimal>.
1086 =head2 $c->get_auth_store( $name )
1088 Return the store whose name is $name.
1090 =head2 $c->get_auth_store_name( $store )
1092 Return the name of the store $store.
1094 =head2 $c->auth_stores( )
1096 A hash keyed by name, with the stores registered in the app.
1098 =head2 $c->register_auth_stores( %stores_by_name )
1100 Register stores into the application.
1102 =head2 $c->auth_store_names( )
1104 =head2 $c->get_user( )
1108 Yuval Kogman, C<nothingmuch@woobling.org>
1110 Jay Kuri, C<jayk@cpan.org>
1116 Tomas Doran (t0m), C<bobtfish@bobtfish.net>
1122 =head1 COPYRIGHT & LICENSE
1124 Copyright (c) 2005 the aforementioned authors. All rights
1125 reserved. This program is free software; you can redistribute
1126 it and/or modify it under the same terms as Perl itself.