1 package Catalyst::Plugin::Authentication;
6 use Catalyst::Authentication::Realm;
7 use namespace::autoclean;
9 has _user => ( is => 'rw' );
11 our $VERSION = "0.10016";
13 sub set_authenticated {
14 my ( $c, $user, $realmname ) = @_;
17 $c->request->{user} = $user; # compatibility kludge
20 $realmname = 'default';
22 my $realm = $c->get_auth_realm($realmname);
25 Catalyst::Exception->throw(
26 "set_authenticated called with nonexistant realm: '$realmname'.");
28 $user->auth_realm($realm->name);
32 $c->maybe::next::method($user, $realmname);
42 if ( defined($c->_user) ) {
45 return $c->auth_restore_user;
49 # change this to allow specification of a realm - to verify the user is part of that realm
50 # in addition to verifying that they exist.
53 return defined($c->_user) || defined($c->find_realm_for_persisted_user);
56 # works like user_exists - except only returns true if user
57 # exists AND is in the realm requested.
59 my ($c, $realmname) = @_;
61 if (defined($c->_user)) {
62 return ($c->_user->auth_realm eq $realmname);
64 my $realm = $c->find_realm_for_persisted_user;
66 return ($realm->name eq $realmname);
73 sub __old_save_user_in_session {
74 my ( $c, $user, $realmname ) = @_;
76 $c->session->{__user_realm} = $realmname;
78 # we want to ask the store for a user prepared for the session.
79 # but older modules split this functionality between the user and the
80 # store. We try the store first. If not, we use the old method.
81 my $realm = $c->get_auth_realm($realmname);
82 if ($realm->{'store'}->can('for_session')) {
83 $c->session->{__user} = $realm->{'store'}->for_session($c, $user);
85 $c->session->{__user} = $user->for_session;
92 if ($c->user_exists) {
94 ## if we have a valid session handler - we store the
95 ## realm in the session. If not - we have to hope that
96 ## the realm can recognize its frozen user somehow.
97 if ($c->can('session') &&
98 $c->config->{'Plugin::Authentication'}{'use_session'} &&
99 $c->session_is_valid) {
101 $c->session->{'__user_realm'} = $c->_user->auth_realm;
104 my $realm = $c->get_auth_realm($c->_user->auth_realm);
106 # used to call $realm->save_user_in_session
107 $realm->persist_user($c, $c->user);
112 ## this was a short lived method to update user information -
113 ## you should use persist_user instead.
114 sub update_user_in_session {
117 return $c->persist_user;
125 my $realm = $c->find_realm_for_persisted_user;
127 $realm->remove_persisted_user($c);
130 $c->maybe::next::method(@_);
134 my ( $c, $userinfo, $realmname ) = @_;
136 $realmname ||= 'default';
137 my $realm = $c->get_auth_realm($realmname);
140 Catalyst::Exception->throw(
141 "find_user called with nonexistant realm: '$realmname'.");
143 return $realm->find_user($userinfo, $c);
146 ## Consider making this a public method. - would make certain things easier when
147 ## dealing with things pre-auth restore.
148 sub find_realm_for_persisted_user {
152 if ($c->can('session')
153 and $c->config->{'Plugin::Authentication'}{'use_session'}
154 and $c->session_is_valid
155 and exists($c->session->{'__user_realm'})) {
157 $realm = $c->auth_realms->{$c->session->{'__user_realm'}};
158 if ($realm->user_is_restorable($c)) {
162 ## we have no choice but to ask each realm whether it has a persisted user.
163 foreach my $realmname (@{$c->_auth_realm_restore_order}) {
164 my $realm = $c->auth_realms->{$realmname}
165 || Catalyst::Exception->throw("Could not find authentication realm '$realmname'");
167 if $realm->user_is_restorable($c);
173 sub auth_restore_user {
174 my ( $c, $frozen_user, $realmname ) = @_;
177 if (defined($realmname)) {
178 $realm = $c->get_auth_realm($realmname);
180 $realm = $c->find_realm_for_persisted_user;
182 return undef unless $realm; # FIXME die unless? This is an internal inconsistency
184 $c->_user( my $user = $realm->restore_user( $c, $frozen_user ) );
186 # this sets the realm the user originated in.
187 $user->auth_realm($realm->name) if $user;
193 # We can't actually do our setup in setup because the model has not yet been loaded.
194 # So we have to trigger before 'setup_finalize'.
198 $app->mk_classdata('_auth_initialized');
199 $app->_authentication_initialize();
200 $app->next::method(@_);
203 ## the actual initialization routine. whee.
204 sub _authentication_initialize {
207 ## let's avoid recreating / configuring everything if we have already done it, eh?
208 if ($app->can('_auth_realms')) { return };
210 ## make classdata where it is used.
211 $app->mk_classdata( '_auth_realms' => {});
213 ## the order to attempt restore in - If we don't have session - we have
214 ## no way to be sure where a frozen user came from - so we have to
215 ## ask each realm if it can restore the user. Unfortunately it is possible
216 ## that multiple realms could restore the user from the data we have -
217 ## So we have to determine at setup time what order to ask the realms in.
218 ## The default is to use the user_restore_priority values defined in the realm
219 ## config. if they are not defined - we go by alphabetical order. Note that
220 ## the 'default' realm always gets first chance at it unless it is explicitly
221 ## placed elsewhere by user_restore_priority. Remember this only comes
222 ## into play if session is disabled.
224 $app->mk_classdata( '_auth_realm_restore_order' => []);
226 my $cfg = $app->config->{'Plugin::Authentication'};
228 if (!defined($cfg)) {
229 if (exists($app->config->{'authentication'})) {
230 $cfg = $app->config->{'authentication'};
231 $app->config->{'Plugin::Authentication'} = $app->config->{'authentication'};
236 # the realmshash contains the various configured realms. By default this is
237 # the main $app->config->{'Plugin::Authentication'} hash - but if that is
238 # not defined, or there is a subkey {'realms'} then we use that.
242 ## If we have a sub-key of {'realms'} then we use that for realm configuration
243 if (exists($cfg->{'realms'})) {
244 $realmshash = $cfg->{'realms'};
247 # old default was to force use_session on. This must remain for that
248 # reason - but if use_session is already in the config, we respect its setting.
249 if (!exists($cfg->{'use_session'})) {
250 $cfg->{'use_session'} = 1;
253 ## if we have a realms hash
254 if (ref($realmshash) eq 'HASH') {
256 my %auth_restore_order;
258 my $defaultrealm = 'default';
260 foreach my $realm (sort keys %{$realmshash}) {
261 if (ref($realmshash->{$realm}) eq 'HASH' &&
262 (exists($realmshash->{$realm}{credential}) || exists($realmshash->{$realm}{class}))) {
264 $app->setup_auth_realm($realm, $realmshash->{$realm});
266 if (exists($realmshash->{$realm}{'user_restore_priority'})) {
267 $auth_restore_order{$realm} = $realmshash->{$realm}{'user_restore_priority'};
269 $auth_restore_order{$realm} = $authcount++;
274 # if we have a 'default_realm' in the config hash and we don't already
275 # have a realm called 'default', we point default at the realm specified
276 if (exists($cfg->{'default_realm'}) && !$app->get_auth_realm('default')) {
277 if ($app->_set_default_auth_realm($cfg->{'default_realm'})) {
278 $defaultrealm = $cfg->{'default_realm'};
279 $auth_restore_order{'default'} = $auth_restore_order{$cfg->{'default_realm'}};
280 delete($auth_restore_order{$cfg->{'default_realm'}});
284 ## if the default realm did not have a defined priority in its config - we put it at the front.
285 if (!exists($realmshash->{$defaultrealm}{'user_restore_priority'})) {
286 $auth_restore_order{'default'} = 1;
289 @{$app->_auth_realm_restore_order} = sort { $auth_restore_order{$a} <=> $auth_restore_order{$b} } keys %auth_restore_order;
293 ## BACKWARDS COMPATIBILITY - if realms is not defined - then we are probably dealing
294 ## with an old-school config. The only caveat here is that we must add a classname
296 ## also - we have to treat {store} as {stores}{default} - because
297 ## while it is not a clear as a valid config in the docs, it
298 ## is functional with the old api. Whee!
299 if (exists($cfg->{'store'}) && !exists($cfg->{'stores'}{'default'})) {
300 $cfg->{'stores'}{'default'} = $cfg->{'store'};
303 push @{$app->_auth_realm_restore_order}, 'default';
304 foreach my $storename (keys %{$cfg->{'stores'}}) {
306 store => { class => $cfg->{'stores'}{$storename} },
308 $app->setup_auth_realm($storename, $realmcfg);
315 sub setup_auth_realm {
316 my ($app, $realmname, $config) = @_;
318 my $realmclass = $config->{class};
321 $realmclass = 'Catalyst::Authentication::Realm';
322 } elsif ($realmclass !~ /^\+(.*)$/ ) {
323 $realmclass = "Catalyst::Authentication::Realm::${realmclass}";
328 Catalyst::Utils::ensure_class_loaded( $realmclass );
330 my $realm = $realmclass->new($realmname, $config, $app);
332 $app->auth_realms->{$realmname} = $realm;
334 $app->log->debug("realm initialization for '$realmname' failed.");
341 $self->_authentication_initialize(); # Ensure _auth_realms created!
342 return($self->_auth_realms);
346 my ($app, $realmname) = @_;
347 return $app->auth_realms->{$realmname};
351 # Very internal method. Vital Valuable Urgent, Do not touch on pain of death.
352 # Using this method just assigns the default realm to be the value associated
353 # with the realmname provided. It WILL overwrite any real realm called 'default'
354 # so can be very confusing if used improperly. It's used properly already.
355 # Translation: don't use it.
356 sub _set_default_auth_realm {
357 my ($app, $realmname) = @_;
359 if (exists($app->auth_realms->{$realmname})) {
360 $app->auth_realms->{'default'} = $app->auth_realms->{$realmname};
362 return $app->get_auth_realm('default');
366 my ($app, $userinfo, $realmname) = @_;
369 $realmname = 'default';
372 my $realm = $app->get_auth_realm($realmname);
374 ## note to self - make authenticate throw an exception if realm is invalid.
377 return $realm->authenticate($app, $userinfo);
379 Catalyst::Exception->throw(
380 "authenticate called with nonexistant realm: '$realmname'.");
386 ## BACKWARDS COMPATIBILITY -- Warning: Here be monsters!
388 # What follows are backwards compatibility routines - for use with Stores and Credentials
389 # that have not been updated to work with C::P::Authentication v0.10.
390 # These are here so as to not break people's existing installations, but will go away
391 # in a future version.
393 # The old style of configuration only supports a single store, as each store module
394 # sets itself as the default store upon being loaded. This is the only supported
395 # 'compatibility' mode.
399 my ( $c, $uid, @rest ) = @_;
401 return $c->find_user( {'id' => $uid, 'rest'=>\@rest }, 'default' );
405 ## this should only be called when using old-style authentication plugins. IF this gets
406 ## called in a new-style config - it will OVERWRITE the store of your default realm. Don't do it.
407 ## also - this is a partial setup - because no credential is instantiated... in other words it ONLY
408 ## works with old-style auth plugins and C::P::Authentication in compatibility mode. Trying to combine
409 ## this with a realm-type config will probably crash your app.
410 sub default_auth_store {
413 my $realm = $self->get_auth_realm('default');
415 $realm = $self->setup_auth_realm('default', { class => 'Compatibility' });
417 if ( my $new = shift ) {
422 $storeclass = ref($new);
427 # BACKWARDS COMPATIBILITY - if the store class does not define find_user, we define it in terms
428 # of get_user and add it to the class. this is because the auth routines use find_user,
429 # and rely on it being present. (this avoids per-call checks)
430 if (!$storeclass->can('find_user')) {
432 *{"${storeclass}::find_user"} = sub {
433 my ($self, $info) = @_;
434 my @rest = @{$info->{rest}} if exists($info->{rest});
435 $self->get_user($info->{id}, @rest);
440 return $self->get_auth_realm('default')->store;
443 ## BACKWARDS COMPATIBILITY
444 ## this only ever returns a hash containing 'default' - as that is the only
445 ## supported mode of calling this.
446 sub auth_store_names {
449 my %hash = ( $self->get_auth_realm('default')->store => 'default' );
453 my ( $self, $name ) = @_;
455 if ($name ne 'default') {
456 Carp::croak "get_auth_store called on non-default realm '$name'. Only default supported in compatibility mode";
458 $self->default_auth_store();
462 sub get_auth_store_name {
463 my ( $self, $store ) = @_;
467 # sub auth_stores is only used internally - here for completeness
471 my %hash = ( 'default' => $self->get_auth_realm('default')->store);
482 Catalyst::Plugin::Authentication - Infrastructure plugin for the Catalyst
483 authentication framework.
492 $c->authenticate({ username => 'myusername',
493 password => 'mypassword' });
494 my $age = $c->user->get('age');
499 The authentication plugin provides generic user support for Catalyst apps. It
500 is the basis for both authentication (checking the user is who they claim to
501 be), and authorization (allowing the user to do what the system authorises
504 Using authentication is split into two parts. A Store is used to actually
505 store the user information, and can store any amount of data related to the
506 user. Credentials are used to verify users, using information from the store,
507 given data from the frontend. A Credential and a Store are paired to form a
508 'Realm'. A Catalyst application using the authentication framework must have
509 at least one realm, and may have several.
511 To implement authentication in a Catalyst application you need to add this
512 module, and specify at least one realm in the configuration.
514 Authentication data can also be stored in a session, if the application
515 is using the L<Catalyst::Plugin::Session> module.
517 B<NOTE> in version 0.10 of this module, the interface to this module changed.
518 Please see L</COMPATIBILITY ROUTINES> for more information.
522 =head2 The Authentication/Authorization Process
524 Web applications typically need to identify a user - to tell the user apart
525 from other users. This is usually done in order to display private information
526 that is only that user's business, or to limit access to the application so
527 that only certain entities can access certain parts.
529 This process is split up into several steps. First you ask the user to identify
530 themselves. At this point you can't be sure that the user is really who they
533 Then the user tells you who they are, and backs this claim with some piece of
534 information that only the real user could give you. For example, a password is
535 a secret that is known to both the user and you. When the user tells you this
536 password you can assume they're in on the secret and can be trusted (ignore
537 identity theft for now). Checking the password, or any other proof is called
538 B<credential verification>.
540 By this time you know exactly who the user is - the user's identity is
541 B<authenticated>. This is where this module's job stops, and your application
542 or other plugins step in.
544 The next logical step is B<authorization>, the process of deciding what a user
545 is (or isn't) allowed to do. For example, say your users are split into two
546 main groups - regular users and administrators. You want to verify that the
547 currently logged in user is indeed an administrator before performing the
548 actions in an administrative part of your application. These decisions may be
549 made within your application code using just the information available after
550 authentication, or it may be facilitated by a number of plugins.
552 =head2 The Components In This Framework
556 Configuration of the Catalyst::Plugin::Authentication framework is done in
557 terms of realms. In simplest terms, a realm is a pairing of a Credential
558 verifier and a User storage (Store) backend. As of version 0.10003, realms are
559 now objects that you can create and customize.
561 An application can have any number of Realms, each of which operates
562 independent of the others. Each realm has a name, which is used to identify it
563 as the target of an authentication request. This name can be anything, such as
564 'users' or 'members'. One realm must be defined as the default_realm, which is
565 used when no realm name is specified. More information about configuring
566 realms is available in the configuration section.
568 =head3 Credential Verifiers
570 When user input is transferred to the L<Catalyst> application
571 (typically via form inputs) the application may pass this information
572 into the authentication system through the C<< $c->authenticate() >>
573 method. From there, it is passed to the appropriate Credential
576 These plugins check the data, and ensure that it really proves the user is who
579 Credential verifiers compatible with versions of this module 0.10x and
580 upwards should be in the namespace
581 C<Catalyst::Authentication::Credential>.
583 =head3 Storage Backends
585 The authentication data also identifies a user, and the Storage backend modules
586 use this data to locate and return a standardized object-oriented
587 representation of a user.
589 When a user is retrieved from a store it is not necessarily authenticated.
590 Credential verifiers accept a set of authentication data and use this
591 information to retrieve the user from the store they are paired with.
593 Storage backends compatible with versions of this module 0.10x and
594 upwards should be in the namespace
595 C<Catalyst::Authentication::Store>.
597 =head3 The Core Plugin
599 This plugin on its own is the glue, providing realm configuration, session
600 integration, and other goodness for the other plugins.
604 More layers of plugins can be stacked on top of the authentication code. For
605 example, L<Catalyst::Plugin::Session::PerUser> provides an abstraction of
606 browser sessions that is more persistent per user.
607 L<Catalyst::Plugin::Authorization::Roles> provides an accepted way to separate
608 and group users into categories, and then check which categories the current
613 Let's say we were storing users in a simple Perl hash. Users are
614 verified by supplying a password which is matched within the hash.
616 This means that our application will begin like this:
624 __PACKAGE__->config( 'Plugin::Authentication' =>
629 password_field => 'password',
630 password_type => 'clear'
636 password => "s00p3r",
638 roles => [qw/edit delete/],
641 password => "s3cr3t",
642 roles => [qw/comment/],
650 This tells the authentication plugin what realms are available, which
651 credential and store modules are used, and the configuration of each. With
652 this code loaded, we can now attempt to authenticate users.
654 To show an example of this, let's create an authentication controller:
656 package MyApp::Controller::Auth;
659 my ( $self, $c ) = @_;
661 if ( my $user = $c->req->params->{user}
662 and my $password = $c->req->params->{password} )
664 if ( $c->authenticate( { username => $user,
665 password => $password } ) ) {
666 $c->res->body( "hello " . $c->user->get("name") );
676 This code should be self-explanatory. If all the necessary fields are supplied,
677 call the C<authenticate> method on the context object. If it succeeds the
680 The credential verifier will attempt to retrieve the user whose
681 details match the authentication information provided to
682 C<< $c->authenticate() >>. Once it fetches the user the password is
683 checked and if it matches the user will be B<authenticated> and
684 C<< $c->user >> will contain the user object retrieved from the store.
686 In the above case, the default realm is checked, but we could just as easily
687 check an alternate realm. If this were an admin login, for example, we could
688 authenticate on the admin realm by simply changing the C<< $c->authenticate() >>
691 if ( $c->authenticate( { username => $user,
692 password => $password }, 'admin' ) ) {
693 $c->res->body( "hello " . $c->user->get("name") );
697 Now suppose we want to restrict the ability to edit to a user with an
698 'editor' value of yes.
700 The restricted action might look like this:
703 my ( $self, $c ) = @_;
705 $c->detach("unauthorized")
706 unless $c->user_exists
707 and $c->user->get('editor') eq 'yes';
709 # do something restricted here
712 (Note that if you have multiple realms, you can use
713 C<< $c->user_in_realm('realmname') >> in place of
714 C<< $c->user_exists(); >> This will essentially perform the same
715 verification as user_exists, with the added requirement that if there
716 is a user, it must have come from the realm specified.)
718 The above example is somewhat similar to role based access control.
719 L<Catalyst::Authentication::Store::Minimal> treats the roles field as
720 an array of role names. Let's leverage this. Add the role authorization
729 my ( $self, $c ) = @_;
731 $c->detach("unauthorized") unless $c->check_user_roles("edit");
733 # do something restricted here
736 This is somewhat simpler and will work if you change your store, too, since the
737 role interface is consistent.
739 Let's say your app grows, and you now have 10,000 users. It's no longer
740 efficient to maintain a hash of users, so you move this data to a database.
741 You can accomplish this simply by installing the L<DBIx::Class|Catalyst::Authentication::Store::DBIx::Class> Store and
742 changing your config:
744 __PACKAGE__->config( 'Plugin::Authentication' =>
746 default_realm => 'members',
750 password_field => 'password',
751 password_type => 'clear'
754 class => 'DBIx::Class',
755 user_model => 'MyApp::Users',
756 role_column => 'roles',
762 The authentication system works behind the scenes to load your data from the
763 new source. The rest of your application is completely unchanged.
769 __PACKAGE__->config( 'Plugin::Authentication' =>
771 default_realm => 'members',
776 password_field => 'password',
777 password_type => 'clear'
780 class => 'DBIx::Class',
781 user_model => 'MyApp::Users',
782 role_column => 'roles',
788 password_field => 'password',
789 password_type => 'clear'
792 class => '+MyApp::Authentication::Store::NetAuth',
793 authserver => '192.168.10.17'
799 NOTE: Until version 0.10008 of this module, you would need to put all the
800 realms inside a "realms" key in the configuration. Please see
801 L</COMPATIBILITY CONFIGURATION> for more information
807 Whether or not to store the user's logged in state in the session, if the
808 application is also using L<Catalyst::Plugin::Session>. This
809 value is set to true per default.
811 However, even if use_session is disabled, if any code touches $c->session, a session
812 object will be auto-vivified and session Cookies will be sent in the headers. To
813 prevent accidental session creation, check if a session already exists with
814 if ($c->sessionid) { ... }. If the session doesn't exist, then don't place
815 anything in the session to prevent an unecessary session from being created.
819 This defines which realm should be used as when no realm is provided to methods
820 that require a realm such as authenticate or find_user.
824 The Plugin::Authentication config hash contains the series of realm
825 configurations you want to use for your app. The only rule here is
826 that there must be at least one. A realm consists of a name, which is used
827 to reference the realm, a credential and a store. You may also put your
828 realm configurations within a subelement called 'realms' if you desire to
829 separate them from the remainder of your configuration. Note that if you use
830 a 'realms' subelement, you must put ALL of your realms within it.
832 You can also specify a realm class to instantiate instead of the default
833 L<Catalyst::Authentication::Realm> class using the 'class' element within the
836 Each realm config contains two hashes, one called 'credential' and one called
837 'store', each of which provide configuration details to the respective modules.
838 The contents of these hashes is specific to the module being used, with the
839 exception of the 'class' element, which tells the core Authentication module the
840 classname to instantiate.
842 The 'class' element follows the standard Catalyst mechanism of class
843 specification. If a class is prefixed with a +, it is assumed to be a complete
844 class name. Otherwise it is considered to be a portion of the class name. For
845 credentials, the classname 'B<Password>', for example, is expanded to
846 Catalyst::Authentication::Credential::B<Password>. For stores, the
847 classname 'B<storename>' is expanded to:
848 Catalyst::Authentication::Store::B<storename>.
854 =head2 $c->authenticate( $userinfo [, $realm ])
856 Attempts to authenticate the user using the information in the $userinfo hash
857 reference using the realm $realm. $realm may be omitted, in which case the
858 default realm is checked.
862 Returns the currently logged in user, or undef if there is none.
864 =head2 $c->user_exists( )
866 Returns true if a user is logged in right now. The difference between
867 user_exists and user is that user_exists will return true if a user is logged
868 in, even if it has not been yet retrieved from the storage backend. If you only
869 need to know if the user is logged in, depending on the storage mechanism this
870 can be much more efficient.
872 =head2 $c->user_in_realm( $realm )
874 Works like user_exists, except that it only returns true if a user is both
875 logged in right now and was retrieved from the realm provided.
879 Logs the user out. Deletes the currently logged in user from C<< $c->user >>
880 and the session. It does not delete the session.
882 =head2 $c->find_user( $userinfo, $realm )
884 Fetch a particular users details, matching the provided user info, from the realm
887 =head2 persist_user()
889 Under normal circumstances the user data is only saved to the session during
890 initial authentication. This call causes the auth system to save the
891 currently authenticated user's data across requests. Useful if you have
892 changed the user data and want to ensure that future requests reflect the
893 most current data. Assumes that at the time of this call, $c->user
894 contains the most current data.
896 =head2 find_realm_for_persisted_user()
898 Private method, do not call from user code!
900 =head1 INTERNAL METHODS
902 These methods are for Catalyst::Plugin::Authentication B<INTERNAL USE> only.
903 Please do not use them in your own code, whether application or credential /
904 store modules. If you do, you will very likely get the nasty shock of having
905 to fix / rewrite your code when things change. They are documented here only
908 =head2 $c->set_authenticated( $user, $realmname )
910 Marks a user as authenticated. This is called from within the authenticate
911 routine when a credential returns a user. $realmname defaults to 'default'
913 =head2 $c->auth_restore_user( $user, $realmname )
915 Used to restore a user from the session. In most cases this is called without
916 arguments to restore the user via the session. Can be called with arguments
917 when restoring a user from some other method. Currently not used in this way.
919 =head2 $c->auth_realms( )
921 Returns a hashref containing realmname -> realm instance pairs. Realm
922 instances contain an instantiated store and credential object as the 'store'
923 and 'credential' elements, respectively
925 =head2 $c->get_auth_realm( $realmname )
927 Retrieves the realm instance for the realmname provided.
929 =head2 $c->update_user_in_session
931 This was a short-lived method to update user information - you should use persist_user instead.
933 =head2 $c->setup_auth_realm( )
935 =head1 OVERRIDDEN METHODS
941 This list might not be up to date. Below are modules known to work with the updated
942 API of 0.10 and are therefore compatible with realms.
946 L<Catalyst::Authentication::Realm>
948 =head2 User Storage Backends
952 =item L<Catalyst::Authentication::Store::Minimal>
954 =item L<Catalyst::Authentication::Store::DBIx::Class>
956 =item L<Catalyst::Authentication::Store::LDAP>
958 =item L<Catalyst::Authentication::Store::RDBO>
960 =item L<Catalyst::Authentication::Store::Model::KiokuDB>
962 =item L<Catalyst::Authentication::Store::Jifty::DBI>
964 =item L<Catalyst::Authentication::Store::Htpasswd>
968 =head2 Credential verification
972 =item L<Catalyst::Authentication::Credential::Password>
974 =item L<Catalyst::Authentication::Credential::HTTP>
976 =item L<Catalyst::Authentication::Credential::OpenID>
978 =item L<Catalyst::Authentication::Credential::Authen::Simple>
980 =item L<Catalyst::Authentication::Credential::Flickr>
982 =item L<Catalyst::Authentication::Credential::Testing>
984 =item L<Catalyst::Authentication::Credential::AuthTkt>
986 =item L<Catalyst::Authentication::Credential::Kerberos>
992 L<Catalyst::Plugin::Authorization::ACL>,
993 L<Catalyst::Plugin::Authorization::Roles>
995 =head2 Internals Documentation
997 L<Catalyst::Plugin::Authentication::Internals>
1001 L<Catalyst::Plugin::Session>,
1002 L<Catalyst::Plugin::Session::PerUser>
1004 =head1 DON'T SEE ALSO
1006 This module along with its sub plugins deprecate a great number of other
1007 modules. These include L<Catalyst::Plugin::Authentication::Simple>,
1008 L<Catalyst::Plugin::Authentication::CDBI>.
1010 =head1 INCOMPATABILITIES
1012 The realms-based configuration and functionality of the 0.10 update
1013 of L<Catalyst::Plugin::Authentication> required a change in the API used by
1014 credentials and stores. It has a compatibility mode which allows use of
1015 modules that have not yet been updated. This, however, completely mimics the
1016 older api and disables the new realm-based features. In other words you cannot
1017 mix the older credential and store modules with realms, or realm-based
1018 configs. The changes required to update modules are relatively minor and are
1019 covered in L<Catalyst::Plugin::Authentication::Internals>. We hope that most
1020 modules will move to the compatible list above very quickly.
1022 =head1 COMPATIBILITY CONFIGURATION
1024 Until version 0.10008 of this module, you needed to put all the
1025 realms inside a "realms" key in the configuration.
1028 __PACKAGE__->config( 'Plugin::Authentication' =>
1030 default_realm => 'members',
1039 If you use the old, deprecated C<< __PACKAGE__->config( 'authentication' ) >>
1040 configuration key, then the realms key is still required.
1042 =head1 COMPATIBILITY ROUTINES
1044 In version 0.10 of L<Catalyst::Plugin::Authentication>, the API
1045 changed. For app developers, this change is fairly minor, but for
1046 Credential and Store authors, the changes are significant.
1048 Please see the documentation in version 0.09 of
1049 Catalyst::Plugin::Authentication for a better understanding of how the old API
1052 The items below are still present in the plugin, though using them is
1053 deprecated. They remain only as a transition tool, for those sites which can
1054 not yet be upgraded to use the new system due to local customizations or use
1055 of Credential / Store modules that have not yet been updated to work with the
1058 These routines should not be used in any application using realms
1059 functionality or any of the methods described above. These are for reference
1064 This method is used to initiate authentication and user retrieval. Technically
1065 this is part of the old Password credential module and it still resides in the
1066 L<Password|Catalyst::Plugin::Authentication::Credential::Password> class. It is
1067 included here for reference only.
1069 =head2 $c->default_auth_store( )
1071 Return the store whose name is 'default'.
1073 This is set to C<< $c->config( 'Plugin::Authentication' => { store => # Store} ) >> if that value exists,
1074 or by using a Store plugin:
1076 # load the Minimal authentication store.
1077 use Catalyst qw/Authentication Authentication::Store::Minimal/;
1079 Sets the default store to
1080 L<Catalyst::Plugin::Authentication::Store::Minimal>.
1082 =head2 $c->get_auth_store( $name )
1084 Return the store whose name is $name.
1086 =head2 $c->get_auth_store_name( $store )
1088 Return the name of the store $store.
1090 =head2 $c->auth_stores( )
1092 A hash keyed by name, with the stores registered in the app.
1094 =head2 $c->register_auth_stores( %stores_by_name )
1096 Register stores into the application.
1098 =head2 $c->auth_store_names( )
1100 =head2 $c->get_user( )
1104 Yuval Kogman, C<nothingmuch@woobling.org>
1106 Jay Kuri, C<jayk@cpan.org>
1112 Tomas Doran (t0m), C<bobtfish@bobtfish.net>
1118 Florian Ragwitz C<rafl@debian.org>
1120 Stephan Jauernick C<stephanj@cpan.org>
1122 =head1 COPYRIGHT & LICENSE
1124 Copyright (c) 2005 - 2009
1125 the Catalyst::Plugin::Authentication L</AUTHORS>
1128 This program is free software; you can redistribute
1129 it and/or modify it under the same terms as Perl itself.