Fixing POD

[catagits/Catalyst-Authentication-Realm-Adaptor.git] / lib / Catalyst / Authentication / Realm / Adaptor.pm

diff --git a/lib/Catalyst/Authentication/Realm/Adaptor.pm b/lib/Catalyst/Authentication/Realm/Adaptor.pm
index bf01894..59450ec 100644 (file)
--- a/lib/Catalyst/Authentication/Realm/Adaptor.pm
+++ b/lib/Catalyst/Authentication/Realm/Adaptor.pm
@@ -106,9 +106,9 @@ sub find_user {
                 Catalyst::Exception->throw(__PACKAGE__ . " realm: " . $self->name . "'s store_adaptor is configured to use a code ref that doesn't exist");
             }
         }
-        return $self->SUPER::authenticate($c, $newauthinfo);
+        return $self->SUPER::find_user($c, $newauthinfo);
     } else {
-        return $self->SUPER::authenticate($c, $authinfo);
+        return $self->SUPER::find_user($c, $authinfo);
     }
 }
 
@@ -233,7 +233,7 @@ with a status of either 'temporary' or 'active.'
 
 This realm works by intercepting the original authentication information
 between the time C<< $c->authenticate($authinfo) >> is called and the time the
-realm's C<$realm->authenticate($c,$authinfo)> method is called, allowing for
+realm's C<< $realm->authenticate($c,$authinfo) >> method is called, allowing for
 the $authinfo parameter to be modified or replaced as your application
 requires. It can also operate after the call to the credential's
 C<authenticate()> method but before the call to the store's C<find_user>
@@ -248,7 +248,7 @@ credential and store options.
 
 This module can operate in two points during authentication processing. 
 The first is prior the realm's C<authenticate> call (immediately after the call to
-C<<$c->authenticate()>>.) To operate here, your filter options should go in a hash
+C<< $c->authenticate() >>.) To operate here, your filter options should go in a hash
 under the key C<credential_adaptor>.
 
 The second point is after the call to credential's C<authenticate> method but
@@ -404,7 +404,7 @@ be better solved by adjusting your credential or store directly.
 That said, there are some areas where this module can be particularly useful. 
 For example, this module allows for global application of additional arguments
 to authinfo for a certain realm via your config.  It also allows for preliminary
-testing of alternate configs before you adjust every C<<$c->authenticate()>> call 
+testing of alternate configs before you adjust every C<< $c->authenticate() >> call 
 within your application.
 
 It is also useful when combined with the various external authentication
@@ -425,7 +425,7 @@ even with Catalyst's flexible authentication system.
 With all of that said, caution is warranted when using this module.  It modifies
 the behavior of the application in ways that are not obvious and can therefore
 lead to extremely hard to track-down bugs.  This is especially true when using 
-the C<action> filter method.  When a developer calls C<<$c->authenticate()>> 
+the C<action> filter method.  When a developer calls C<< $c->authenticate() >> 
 they are not expecting any actions to be called before it returns.  
 
 If you use the C<action> method, I strongly recommend that you use it only as a