Trim whitespace
[catagits/Catalyst-Plugin-Authentication.git] / lib / Catalyst / Authentication / Credential / Password.pm
CommitLineData
5c5af345 1package Catalyst::Authentication::Credential::Password;
2
3use strict;
4use warnings;
5
6use base qw/Class::Accessor::Fast/;
7
8use Scalar::Util ();
9use Catalyst::Exception ();
10use Digest ();
11
6c9482fe 12__PACKAGE__->mk_accessors(qw/_config realm/);
5c5af345 13
14sub new {
15 my ($class, $config, $app, $realm) = @_;
2c49ad4e 16
17 # Note _config is horrible back compat hackery!
106913db 18 my $self = { _config => $config };
5c5af345 19 bless $self, $class;
38b0fcdb 20
5c5af345 21 $self->realm($realm);
38b0fcdb 22
106913db 23 $self->_config->{'password_field'} ||= 'password';
24 $self->_config->{'password_type'} ||= 'clear';
25 $self->_config->{'password_hash_type'} ||= 'SHA-1';
38b0fcdb 26
106913db 27 my $passwordtype = $self->_config->{'password_type'};
5c5af345 28 if (!grep /$passwordtype/, ('none', 'clear', 'hashed', 'salted_hash', 'crypted', 'self_check')) {
106913db 29 Catalyst::Exception->throw(__PACKAGE__ . " used with unsupported password type: " . $self->_config->{'password_type'});
5c5af345 30 }
31 return $self;
32}
33
34sub authenticate {
35 my ( $self, $c, $realm, $authinfo ) = @_;
36
38b0fcdb 37 ## because passwords may be in a hashed format, we have to make sure that we remove the
38 ## password_field before we pass it to the user routine, as some auth modules use
39 ## all data passed to them to find a matching user...
5c5af345 40 my $userfindauthinfo = {%{$authinfo}};
106913db 41 delete($userfindauthinfo->{$self->_config->{'password_field'}});
38b0fcdb 42
5c5af345 43 my $user_obj = $realm->find_user($userfindauthinfo, $c);
44 if (ref($user_obj)) {
45 if ($self->check_password($user_obj, $authinfo)) {
46 return $user_obj;
47 }
48 } else {
29bd517d 49 $c->log->debug(
f2ef1123 50 'Unable to locate user matching user info provided in realm: '
29bd517d 51 . $realm->name
52 ) if $c->debug;
5c5af345 53 return;
54 }
55}
56
57sub check_password {
58 my ( $self, $user, $authinfo ) = @_;
38b0fcdb 59
106913db 60 if ($self->_config->{'password_type'} eq 'self_check') {
61 return $user->check_password($authinfo->{$self->_config->{'password_field'}});
5c5af345 62 } else {
106913db 63 my $password = $authinfo->{$self->_config->{'password_field'}};
64 my $storedpassword = $user->get($self->_config->{'password_field'});
38b0fcdb 65
106913db 66 if ($self->_config->{'password_type'} eq 'none') {
5c5af345 67 return 1;
106913db 68 } elsif ($self->_config->{'password_type'} eq 'clear') {
38b0fcdb 69 # FIXME - Should we warn in the $storedpassword undef case,
1ae2143a 70 # as the user probably fluffed the config?
71 return unless defined $storedpassword;
5c5af345 72 return $password eq $storedpassword;
38b0fcdb 73 } elsif ($self->_config->{'password_type'} eq 'crypted') {
5c5af345 74 return $storedpassword eq crypt( $password, $storedpassword );
106913db 75 } elsif ($self->_config->{'password_type'} eq 'salted_hash') {
5c5af345 76 require Crypt::SaltedHash;
106913db 77 my $salt_len = $self->_config->{'password_salt_len'} ? $self->_config->{'password_salt_len'} : 0;
5c5af345 78 return Crypt::SaltedHash->validate( $storedpassword, $password,
79 $salt_len );
106913db 80 } elsif ($self->_config->{'password_type'} eq 'hashed') {
5c5af345 81
106913db 82 my $d = Digest->new( $self->_config->{'password_hash_type'} );
83 $d->add( $self->_config->{'password_pre_salt'} || '' );
5c5af345 84 $d->add($password);
106913db 85 $d->add( $self->_config->{'password_post_salt'} || '' );
5c5af345 86
87 my $computed = $d->clone()->digest;
88 my $b64computed = $d->clone()->b64digest;
89 return ( ( $computed eq $storedpassword )
90 || ( unpack( "H*", $computed ) eq $storedpassword )
91 || ( $b64computed eq $storedpassword)
92 || ( $b64computed.'=' eq $storedpassword) );
93 }
94 }
95}
96
5c5af345 97__PACKAGE__;
98
99__END__
100
101=pod
102
103=head1 NAME
104
105Catalyst::Authentication::Credential::Password - Authenticate a user
106with a password.
107
108=head1 SYNOPSIS
109
110 use Catalyst qw/
111 Authentication
112 /;
113
114 package MyApp::Controller::Auth;
115
116 sub login : Local {
117 my ( $self, $c ) = @_;
118
119 $c->authenticate( { username => $c->req->param('username'),
120 password => $c->req->param('password') });
121 }
122
123=head1 DESCRIPTION
124
125This authentication credential checker takes authentication information
126(most often a username) and a password, and attempts to validate the password
127provided against the user retrieved from the store.
128
129=head1 CONFIGURATION
130
131 # example
38b0fcdb 132 __PACKAGE__->config('Plugin::Authentication' =>
133 {
5c5af345 134 default_realm => 'members',
135 realms => {
136 members => {
38b0fcdb 137
5c5af345 138 credential => {
139 class => 'Password',
140 password_field => 'password',
141 password_type => 'hashed',
38b0fcdb 142 password_hash_type => 'SHA-1'
143 },
5c5af345 144 ...
145
146
147The password module is capable of working with several different password
148encryption/hashing algorithms. The one the module uses is determined by the
149credential configuration.
150
151Those who have used L<Catalyst::Plugin::Authentication> prior to the 0.10 release
152should note that the password field and type information is no longer part
153of the store configuration and is now part of the Password credential configuration.
154
38b0fcdb 155=over 4
5c5af345 156
38b0fcdb 157=item class
5c5af345 158
159The classname used for Credential. This is part of
160L<Catalyst::Plugin::Authentication> and is the method by which
161Catalyst::Authentication::Credential::Password is loaded as the
162credential validator. For this module to be used, this must be set to
163'Password'.
164
165=item password_field
166
167The field in the user object that contains the password. This will vary
168depending on the storage class used, but is most likely something like
169'password'. In fact, this is so common that if this is left out of the config,
170it defaults to 'password'. This field is obtained from the user object using
38b0fcdb 171the get() method. Essentially: $user->get('passwordfieldname');
172B<NOTE> If the password_field is something other than 'password', you must
173be sure to use that same field name when calling $c->authenticate().
5c5af345 174
38b0fcdb 175=item password_type
5c5af345 176
177This sets the password type. Often passwords are stored in crypted or hashed
38b0fcdb 178formats. In order for the password module to verify the plaintext password
5c5af345 179passed in, it must be told what format the password will be in when it is retreived
180from the user object. The supported options are:
181
182=over 8
183
184=item none
185
186No password check is done. An attempt is made to retrieve the user based on
38b0fcdb 187the information provided in the $c->authenticate() call. If a user is found,
5c5af345 188authentication is considered to be successful.
189
190=item clear
191
192The password in user is in clear text and will be compared directly.
193
194=item self_check
195
196This option indicates that the password should be passed to the check_password()
38b0fcdb 197routine on the user object returned from the store.
5c5af345 198
199=item crypted
200
38b0fcdb 201The password in user is in UNIX crypt hashed format.
5c5af345 202
203=item salted_hash
204
205The password in user is in salted hash format, and will be validated
206using L<Crypt::SaltedHash>. If this password type is selected, you should
207also provide the B<password_salt_len> config element to define the salt length.
208
209=item hashed
210
211If the user object supports hashed passwords, they will be used in conjunction
212with L<Digest>. The following config elements affect the hashed configuration:
213
214=over 8
215
38b0fcdb 216=item password_hash_type
5c5af345 217
38b0fcdb 218The hash type used, passed directly to L<Digest/new>.
5c5af345 219
38b0fcdb 220=item password_pre_salt
5c5af345 221
222Any pre-salt data to be passed to L<Digest/add> before processing the password.
223
224=item password_post_salt
225
226Any post-salt data to be passed to L<Digest/add> after processing the password.
227
228=back
229
230=back
231
232=back
233
234=head1 USAGE
235
236The Password credential module is very simple to use. Once configured as
237indicated above, authenticating using this module is simply a matter of
238calling $c->authenticate() with an authinfo hashref that includes the
239B<password> element. The password element should contain the password supplied
240by the user to be authenticated, in clear text. The other information supplied
241in the auth hash is ignored by the Password module, and simply passed to the
242auth store to be used to retrieve the user. An example call follows:
243
244 if ($c->authenticate({ username => $username,
245 password => $password} )) {
246 # authentication successful
247 } else {
248 # authentication failed
249 }
250
251=head1 METHODS
252
253There are no publicly exported routines in the Password module (or indeed in
38b0fcdb 254most credential modules.) However, below is a description of the routines
5c5af345 255required by L<Catalyst::Plugin::Authentication> for all credential modules.
256
8a7bd676 257=head2 new( $config, $app, $realm )
5c5af345 258
259Instantiate a new Password object using the configuration hash provided in
260$config. A reference to the application is provided as the second argument.
261Note to credential module authors: new() is called during the application's
262plugin setup phase, which is before the application specific controllers are
263loaded. The practical upshot of this is that things like $c->model(...) will
264not function as expected.
265
266=head2 authenticate( $authinfo, $c )
267
268Try to log a user in, receives a hashref containing authentication information
269as the first argument, and the current context as the second.
270
271=head2 check_password( )
272
5c5af345 273=cut