DBI.pm

## no critic (RCS,VERSION)
package Class::User::DBI;

use 5.008;

use strict;
use warnings;

use Socket qw( inet_ntoa inet_aton );

use List::MoreUtils qw( any );

use Authen::Passphrase::SaltedSHA512;

use Class::User::DBI::DB qw( %USER_QUERY db_run_ex );

our $VERSION = '0.01_002';
$VERSION = eval $VERSION;    ## no critic (eval)

sub new {
    my ( $class, $db_conn, $userid ) = @_;

    # Reject any userid that is either undefined or evaluates to false.
    return if !defined $userid || !$userid;
    my $self = bless {}, $class;
    $self->{_db_conn}    = $db_conn;
    $self->{userid}      = lc $userid;
    $self->{validated}   = 0;            # Start out with a non-validated user.
    $self->{exists_user} = 0;            # Start with an unproven existence.
    return $self;
}

# Accessors.

sub userid {
    my $self = shift;
    return $self->{userid};
}

sub _db_conn {
    my $self = shift;
    return $self->{_db_conn};
}

sub update_email {
    my ( $self, $new_email ) = @_;
    return if !$self->exists_user;
    my $sth =
      $self->_db_run( $USER_QUERY{SQL_update_email}, $new_email,
        $self->userid );
    return $new_email;
}

sub update_username {
    my ( $self, $new_username ) = @_;
    return if !$self->exists_user;
    my $sth = $self->_db_run( $USER_QUERY{SQL_update_username},
        $new_username, $self->userid );
    return $new_username;
}

# Check validated status.  Also allow for invalidation by passing a false
# parameter to the method.
sub validated {
    my ( $self, $new_value ) = @_;
    if ( defined $new_value && !$new_value ) {
        $self->{validated} = 0;
    }
    return $self->{validated};
}

# Prepares and executes a database command using DBIx::Connector's 'run'
# method.  Pass bind values as 2nd+ parameter(s).  If the first bind-value
# element is an array ref, bind value params will be executed in a loop,
# dereferencing each element's list upon execution:
# $self->_db_run( 'SQL GOES HERE', @execute_params ); .... OR....
# $self->_db_run(
#     'SQL GOES HERE',
#     [ first param list ], [ second param list ], ...
# );

sub _db_run {
    my ( $self, $sql, @ex_params ) = @_;
    my $conn = $self->_db_conn;

    # We import db_run_ex() from Class::User::DBI::DB.
    return db_run_ex( $conn, $sql, @ex_params );
}

# Fetches all IP's that are whitelisted for the user.
sub fetch_valid_ips {
    my $self = shift;
    my $sth = $self->_db_run( $USER_QUERY{SQL_fetch_valid_ips}, $self->userid );
    my @rv;
    while ( defined( my $row = $sth->fetchrow_arrayref ) ) {
        if ( defined $row->[0] ) {
            push @rv, inet_ntoa( pack 'N', $row->[0] );
        }
    }
    return @rv;
}

# Fetch user's salt_hex, pass_hex, ip_required, and valid ip's from database.
sub fetch_credentials {
    my $self = shift;
    my $sth =
      $self->_db_run( $USER_QUERY{SQL_fetch_credentials}, $self->userid );
    my ( $salt_hex, $pass_hex, $ip_required ) = $sth->fetchrow_array;
    return if not defined $salt_hex;    # User wasn't found.
    my @valid_ips = $self->fetch_valid_ips;
    return {
        userid      => $self->userid,
        salt_hex    => $salt_hex,
        pass_hex    => $pass_hex,
        ip_required => $ip_required,
        valid_ips   => [@valid_ips],
    };
}

sub validate {
    my ( $self, $password, $ip, $force_revalidate ) = @_;

    # Save ourselves work if user is already authenticated.
    if ( $self->validated ) {
        return $self->userid;
    }
    my $credentials = $self->fetch_credentials;
    my $auth        = Authen::Passphrase::SaltedSHA512->new(
        salt_hex => $credentials->{salt_hex},
        hash_hex => $credentials->{pass_hex}
    );

    # Return undef if password doesn't authenticate for the user.
    return unless $auth->match($password);    ## no critic (postfix)

    # Return undef if an IP is required, and IP param is not in whitelist.
    if ( $credentials->{ip_required} ) {
        ## no critic (postfix)
        return unless defined $ip;            # Reject if no IP param.
        return unless any { $ip eq $_ } @{ $credentials->{valid_ips} };
    }

    # We passed! Authenticate.
    $self->{validated} = 1;    # Set in object that we're authenticated.
    return $self->userid;
}

# Quick check whether a userid exists in the database.
# Return undef if user doesn't exist.
sub exists_user {
    my $self = shift;
    return $self->{exists_user}
      if $self->{exists_user};    # Only query if we have to.
    my $sth = $self->_db_run( $USER_QUERY{SQL_exists_user}, $self->userid );
    return $sth->fetchrow_array;    # Will be undef if user doesn't exist.
}

# May be useful later on if we add user information.
sub load_profile {
    my $self = shift;
    my $sth  = $self->_db_run( $USER_QUERY{SQL_load_profile}, $self->userid );
    my $hr   = $sth->fetchrow_hashref;
    return $hr;
}

sub add_ips {
    my ( $self, @ips ) = @_;
    return if !$self->exists_user;

    # We don't want to insert IP's already in the DB.
    my @ips_in_db = $self->fetch_valid_ips;
    my %uniques;
    @uniques{@ips_in_db} = ();
    my @ips_to_insert = grep { !exists $uniques{$_} } @ips;
    return 0 if !@ips_to_insert;

    # Prepare the userid,ip bundles for our insert query.
    my @execution_param_bundles =
      map { [ $self->userid, unpack( 'N', inet_aton($_) ) ] } @ips_to_insert;
    my $sth =
      $self->_db_run( $USER_QUERY{SQL_add_ips}, @execution_param_bundles );

    return scalar @ips_to_insert;    # Return a count of IP's inserted.
}

sub delete_ips {
    my ( $self, @ips ) = @_;
    return if !$self->exists_user;
    my @ips_in_db = $self->fetch_valid_ips;
    my %found;
    @found{@ips_in_db} = ();
    my @ips_for_deletion = grep { exists $found{$_} } @ips;
    my @execution_param_bundles =
      map { [ $self->userid, unpack( 'N', inet_aton($_) ) ] } @ips_for_deletion;
    my $sth =
      $self->_db_run( $USER_QUERY{SQL_delete_ips}, @execution_param_bundles );
    return scalar @ips_for_deletion;    # Return a count of IP's deleted.
}

sub add_user {
    my ( $self, $userinfo ) = @_;

    my $password = $userinfo->{password};
    return if not length $password;     # We require a password.
    return if $self->exists_user;

    # Default to IP not required.
    my $ip_req   = defined $userinfo->{ip_req}   ? $userinfo->{ip_req}   : 0;
    my $username = defined $userinfo->{username} ? $userinfo->{username} : q{};
    my $email    = defined $userinfo->{email}    ? $userinfo->{email}    : q{};

    my $ips_aref =
      exists( $userinfo->{ips_aref} )
      ? $userinfo->{ips_aref}
      : $userinfo->{ips};               # Detect later if missing.

    return if $ip_req && !ref $ips_aref eq 'ARRAY';

    my $passgen =
      Authen::Passphrase::SaltedSHA512->new( passphrase => $password );
    my $salt_hex = $passgen->salt_hex;
    my $hash_hex = $passgen->hash_hex;
    $self->_db_conn->txn(
        fixup => sub {
            my $sth = $_->prepare( $USER_QUERY{SQL_add_user} );
            $sth->execute( $self->userid, $salt_hex, $hash_hex, $ip_req,
                $username, $email );
            if ( ref($ips_aref) eq 'ARRAY' ) {
                $self->add_ips( @{$ips_aref} );
            }
        }
    );
    $self->{exists_user} = $self->userid;
    return $self->userid;
}

sub update_password {
    my ( $self, $newpass, $oldpass ) = @_;

    return if !$self->exists_user;

    # If an old passphrase is supplied, only update if it validates.
    if ( defined $oldpass ) {
        my $credentials = $self->fetch_credentials;
        my $auth        = Authen::Passphrase::SaltedSHA512->new(
            salt_hex => $credentials->{salt_hex},
            hash_hex => $credentials->{pass_hex}
        );

        # Return undef if password doesn't authenticate for the user.
        return unless $auth->match($oldpass);    ## no critic (postfix)
    }

    my $passgen =
      Authen::Passphrase::SaltedSHA512->new( passphrase => $newpass );
    my $salt_hex = $passgen->salt_hex;
    my $hash_hex = $passgen->hash_hex;
    $self->_db_conn->txn(
        fixup => sub {
            my $sth = $_->prepare( $USER_QUERY{SQL_update_password} );
            $sth->execute( $salt_hex, $hash_hex, $self->userid );
        }
    );
    return $self->userid;
}

sub delete_user {
    my $self = shift;
    return if !$self->exists_user;    # undef if user wasn't in the DB.
    $self->_db_conn->txn(
        fixup => sub {
            my $sth = $_->prepare( $USER_QUERY{SQL_delete_user_users} );
            $sth->execute( $self->userid );
            my $sth2 = $_->prepare( $USER_QUERY{SQL_delete_user_ips} );
            $sth2->execute( $self->userid );
        }
    );
    $self->validated(0);    # Invalidate the deleted user, just in case it was
                            # also the current user.
    $self->{exists_user} = 0;    # Invalidate the exists_user cache.
    return 1;
}

=cut
sub fetch_roles {
    my $self = shift;
    return if !$self->exists_user;
    my $sth = $self->_db_run( $USER_QUERY{SQL_fetch_roles},
        $self->userid );
    my $roles_aoa = $sth->fetchall_arrayref;
    my @roles = map { $_->[0] } @{$roles_aoa};
    return @roles;
}

sub can_role {
    my ( $self, $role ) = @_;
    return if !$self->exists_user;
    my $sth = $self->_db_run( $USER_QUERY{SQL_can_role},
        $self->userid, $role );
    return $sth->fetchrow_array;
}

sub add_roles {
    my ( $self, @roles ) = @_;
    return if !$self->exists_user;
    my @roles_to_insert =
      grep { defined $_ && $_ && !$self->can_role($_) } @roles;
    my @prepared_inserts = map { [ $self->userid, $_ ] } @roles_to_insert;
    my $sth = $self->_db_run( $USER_QUERY{SQL_add_roles},
        @prepared_inserts );
    return scalar @prepared_inserts;
}

sub delete_roles {
    my ( $self, @roles ) = @_;
    return if !$self->exists_user;
    my @roles_to_delete = grep { $self->can_role($_) } @roles;
    my @prepared_deletes = map { [ $self->userid, $_ ] } @roles_to_delete;
    my $sth = $self->_db_run( $USER_QUERY{SQL_delete_roles},
        @prepared_deletes );
    return scalar @prepared_deletes;
}
=cut

# Class methods

sub list_users {
    my ( $class, $conn ) = @_;
    my $self = $class->new( $conn, 'dummy_class_user' );
    my $sth = $self->_db_run( $USER_QUERY{SQL_list_users} );
    return @{ $sth->fetchall_arrayref };
}

sub configure_db {
    my ( $class, $conn ) = @_;
    my @SQL_keys = qw(
      SQL_configure_db_users
      SQL_configure_db_user_ips

    );

    #      Deleted: SQL_configure_db_user_roles
    foreach my $sql_key (@SQL_keys) {
        $conn->run(
            fixup => sub {
                $_->do( $USER_QUERY{$sql_key} );
            }
        );
    }
    return 1;
}

1;

__END__

=head1 NAME

Class::User::DBI - A User class: Login credentials and roles.

=head1 VERSION

Version 0.01_001

=head1 SYNOPSIS

Through a DBIx::Connector object, this module models a "User" class, with
login credentials, and access roles.  Login credentials include a passphrase,
and optionally per user IP whitelisting.

    # Set up a connection using DBIx::Connector:
    # MySQL database settings:

    my $conn = DBIx::Connector->new(
        'dbi:mysql:database=cudbi_tests, 'testing_user', 'testers_pass',
        {
            RaiseError => 1,
            AutoCommit => 1,
        }
    );


    # Now we can play with Class::User::DBI:

    Class::User::DBI->configure_db( $conn );  # Set up the tables for a user DB.

    my @user_list = Class::User::DBI->list_users;

    my $user = new( $conn, $userid );

    my $user_id  = $user->add_user(
        {
            password => $password,
            ip_req   => $bool_ip_req,
            ips      => [ '192.168.0.100', '201.202.100.5' ], # aref ip's.
            username => $full_name,
            email    => $email,
        }
    );

    my $userid      = $user->userid;        # Just returns the object's userid.

    my $validated   = $user->validated;     # The user has been authenticated.

    my $invalidated = $user->validated(0);  # Remove authentication.

    my $is_valid    = $user->validate( $pass, $opt_ips );   # Authenticate the user.

    my $is_valid    = $user->validate( $pass ); # Authentiate without IP.

    my $info_href   = $user->load_profile;   # Load the user's profile.

    my @valid_ips   = $user->fetch_valid_ips;

    my $user_exists = $user->exists_user;

    my $success     = $user->delete_user;

    my $del_count   = $user->delete_ips( @ips );

    my $add_count   = $user->add_ips( @ips );

    my $success     = $user->update_email( 'new@email.address' );

    my $success     = $user->update_username( 'Cool New User Name' );

    my $success     = $user->update_password( 'Old Pass', 'New Pass' );

    my $success     = $user->update_password( 'New Pass' );

    my $can_do      = $user->can_role( $role );

    my $add_count   = $user->add_roles( @roles );

    my $del_count   = $user->delete_roles( @roles );

    my @roles       = $user->fetch_roles;


=head1 DESCRIPTION

The module is designed to simplify user logins, authentication, authorization,
and basic administrative user maintenance.  It stores user credentials, roles,
and basic user information in a database via a DBIx::Connector database
connection.

User passphrases are salted with a 512 bit random salt (unique per user) using
a cryptographically strong random number generator, and converted to a SHA2-512
digest before being stored in the database.  All subsequent passphrase
validation checks test against the salt and passphrase SHA2 hash.

IP whitelists may be maintained per user.  If a user is set to require an IP
check, then the user validates only if his passphrase authenticates AND his
IP is found in the whitelist associated with his user id.

Users may be given zero or more roles.  Roles are simple strings, and may be
used by an authorization framework to determine what aspects of an
application's functionality will be available to a given user, or how the
functionality is presented.

To use, instantiate a user object.  This user's initial state holds only a
userid.  Validate, load user info, load roles, test roles... read on.

=head1 EXPORT

Nothing is exported.  There are many object methods, and three class methods,
described in the next section.


=head1 SUBROUTINES/METHODS


=head2  new
(The constructor -- Class method.)

    my $user_obj = Class::User::DBI->new( $connector, $userid );

Instantiates a new Class::User::DBI object in behalf of a target user on a
database handled by the DBIx::Connector.

The user object may be accessed and manipulated through the methods listed
below.


=head2  fetch_credentials

    my $credentials_href = $user->fetch_credentials;
    my @fields = qw( userid salt_hex pass_hex ip_required );
    foreach my $field ( @fields ) {
        print "$field => $credentials_href->{$field}\n";
    }
    my @valid_ips = @{$valid_ips};
    foreach my $ip ( @valid_ips ) {
        print "Whitelisted IP: $ip\n";
    }

Accepts no parameters.  Returns a hashref holding a small datastructure that
describes the user's credentials.  The structure looks like this:

    $href = {
        userid      => $userid,     # The target user's userid.

        salt_hex    => $salt,       # A 128 hex-character representation of
                                    # the user's random salt.

        pass_hex    => $pass,       # A 128 hex-character representation of
                                    # the user's SHA2-512 digested passphrase.

        ip_required => $ip_req,     # A Boolean value indicating whether this
                                    # user requires IP whitelist validation.

        valid_ips   => [            # Whitelisted IP's for user. (optional)
            '127.0.0.1',                # Some example whitelisted IP's.
            '129.168.0.10',
        ],
    };

A typical usage probably won't require calling this function directly very
often, if at all.  In most cases where it would be useful to look at the salt,
the passphrase digest, and IP whitelists, the
C<< $user->validate( $passphrase, $ip ) >> method is easier to use and less
prone to error.  But for those cases I haven't considered, the
C<fetch_credentials()> method exists.

=head2  load_profile

    my $user_info_href = $user->load_profile;
    foreach my $field ( qw/ userid username email / ) {
        print "$field   => $user_info_href->{$field}\n";
    }

Returns a reference to an anonymous hash containing the user's basic
profile information.  Currently the datastructure looks like this:

    my $user_info_href = {
        userid      => $userid,     # The primary user ID.
        username    => $username,   # The full user name as stored in the DB.
        email       => $email,      # The email stored in the DB for this user.
    };

Although additional fields could be added to the database table and this
module could be subclassed to process those fields, it's probably easier to
just add another table keyed off of the unique C<userid> field, containing
any additional information a given application requires for a user.

=head2  delete_user

    $user->delete_user;

Removes the user from the database, along with the user's IP whitelist, and
roles.  Also sets the C<< $user->validated >>, and C<< $user->exists_user >>
flags to false.


=head2  exists_user

Checks the database to verify that the user exists.  As this method is used
internally frequently its B<positive> result is cached to minimize database
queries.  Methods that would invalidate the existence of the user in the
database, such as C<< $user->delete_user >> will remove the cache entry, and
subsequent tests will access the database on each call to C<exists_user()>,
until such time that the result flips to positive again.

=head2  add_user

    my $success = $self->add_user( {
        username    => $user_full_name,     # Optional field. Default q{}.

        password    => $user_passphrase,    # Clear text password.
                                            # Required field. No length limit.

        email       => $user_email,         # Optional field.  Default q{}.

        ip_req      => $ip_validation_reqd  # Boolean value determining whether
                                            # this user requires IP whitelist
                                            # validation. ( 0 = no, 1 = yes ).
                                            # Optional field.  Default 0.

        ips_aref    => [                    # Optional field.  Default is empty
            '127.0.0.1',                    # list.  If 'ip_req' is set and no
            '192.168.0.1',                  # list is provided here, then valid
        ],                                  # IP's will need to be added later
                                            # before user can validate.
    } );

This method creates a new user in the database with the C<userid> supplied when
the user object was instantiated.  The password field is the only required
field.  It must contain a clear-text passphrase.  There is no length limitation.

Other fields are optional, but convenient.  If IP whitelisting is needed
for this user, the C<ip_req> field must be supplied, and must be set to C<1>
(true).

If C<ip_req> is set to C<1> (true), a list of valid IP's may also be provided
in an arrayref keyed off of C<ips_aref>.  As a convenience, the C<ips> key is
synonymous with C<ips_aref>.  The IP's provided will then be added to the
C<user_ips> database table.  If an IP is required but none are added via
C<add_user>, they will have to be added manually with C<add_ips> before the
user can be validated.

The user's passphrase will be salted with a cryptographically sound random
salt of 512 bits (128 hex digits).  It will then be digested using a SHA2-512
hash, and both the salt and the digest will be stored in the C<users> database.

This is a reliable and secure means of storing a passphrase.  In fact, the
passphrase is not stored at all.  Just a salt and the digest.  Even if the
salt and hash were to be discovered by an attacker, they would not be useful
in side-stepping user validation, as they cannot be used to decrypt the
passphrase.  SHA512 is the strongest of the SHA2 family.  A salt length of
512 bits guarantees a maximum entropy for any given passphrase.

Though it is beyond the scope of this module to do so, users should be
encouraged to use passphrases that are both resistant to dictionary attacks, and
dissimilar to passphrases used in other applications.  No minimum passphrase
size is enforced by this module.  But a strong passphrase should be of ample
length, and should contain characters beyond the standard alphabet.

=head2  update_email

    my $success = $user->update_email( $new_email_address )

Email addresses are not verified for validity in any way.  However, the default
database field used for storing email addresses provides 320 bytes of storage,
which is the maximum length possible for a valid email address.


=head2  update_password

    # Update with validation of old password first.
    my $success = $user->update_password( $new_pass, $old_pass );

    # Update without validation of old password first.
    my $success = $user->update_password( $new_pass );

Using the same algorithms of C< add_user( { password => $passphrase } ); >>,
creates a new password for the user.  If the old passphrase is supplied as
a second parameter, the update will only take place if the old passphrase
validates.

The "with validation" method is useful for allowing a user to update her own
password.  The "without validation" version is useful for allowing an
administrator (or automated process) to reset a user's forgotten password.


=head2  update_username

    my $success = $user->update_username( $new_user_full_name );

There's probably not much need for explaining this method.  The default database
table's C<username> field accepts user names up to fourty characters.


=head2  userid

    my $userid = $user->userid;

A simple accessor returning the C<userid> that is the target of the
C<Class::User::DBI> object.

=head2  validate

    # If no IP whitelist verification is required:
    my $is_valid  = $user->validate( $passphrase );

    # If IP whitelist verification is required:
    my $is_valid = $user->validate( $passphrase, $current_ip );

Returns true if and only if the user can be validated.  What that means will
be described in the paragraphs below.  If the user cannot be validated, the
return value will be C<undef>.  It doesn't matter what the reason for failure
to authenticate might have been: Invalid user ID, invalid password, or
invalid IP address; all three reasons result in a return value of C<undef>.
This behavior encourages the best practice of not divulging to the user why
his authentication failed.  The less information provided, the less an
attacker can user to narrow the field.

=head3 What Validation (or Authentication) Means To This Module

If the user has been configured for no IP testing, validation means that the
C<userid> exists (case insensitively) within the database, and that the
passphrase passed to C<validate()>, when salted with the stored salt and
digested using a SHA2-512 hashing algorithm results in the same 512 bit hash
as the one generated when the passphrase was originally set up.

If the user has been configured to require IP testing, validation I<also> means
that the IP supplied to the C<validate()> method matches one of the IP's stored
in the database for this user.  IP's are stored in the clear, which shouldn't
matter.  User input should never be used for the IP field of C<validate()>.
It is assumed that within the application, the user's IP will be detected, and
that IP will be passed for cross-checking with the whitelist database.

The C<validate()> method caches its B<positive> result.  Any action that might
change the authentication status will remove the cached status.  Actions that
will result in C<validate()> to perform all tests again include
C<delete_user()>, C<update_password()>, or C<validated(0)> (passing the
C<validated()> method a '0'.

=head2  validated

    # Test.
    my $has_been_validated = $user->validated;

    # Invalidate.
    $user->validated(0);

Returns true if the user has been validated, as described above.  Does not
perform a full validation; simply tests whether the previous call to
C<validate()> succeeded, and that nothing has happened to remove that "is valid"
status.

Pass a parameter of 'C<0>' to force all future calls to C<validated()> to return
false.  Also, after resetting C<validated()> to false, future calls to
C<validate()> will go through the full authentication process again until such
time as the authentication is successful.


=head2  fetch_valid_ips

    my @valid_ips = $user->fetch_valid_ips;

Returns a list containing the list of whitelisted IP's for this user.  Each
IP will be a string in the form of C<192.168.0.198>.  If the user doesn't use
IP validation, or there are no IP's stored for this user, the list will be
empty.


=head2  add_ips

    my $quantity_added = $user->add_ips ( @whitelisted_ips );

Pass a list of IP's to add to the IP whitelist for this user.  Any IP's that
are already in the database will be silently skipped.

Returns a count of how many were added.

=head2  delete_ips

    my $quantity_deleted = $user->delete_ips( @ips_to_remove );

Pass a list of IP's to remove from the IP whitelist for this user.  Any IP's
that weren't found in the database will be silently skipped.

Returns a count of how many IP's were dropped.


=head2  fetch_roles

    my @roles = $user->fetch_roles;

Returns a list of roles this user has.  Roles are simply strings that may be
used to identify a resource a user is authorized to access.

=head2  can_role

    my $can_access  = $user->can_role( $role_name );

Returns a true value if the user has the named role.  False otherwise.

=head2  add_roles

    my $quantity_added = $user->add_roles( @list_of_roles );

Pass a list of roles to add for the target user.  Roles already duplicated in
the database will be silently skipped.  Returns a count of how many roles were
added.

=head2  delete_roles

    my $quantity_deleted = $user->delete_roles( @list_of_roles );

Pass a list of roles to delete for the target user.  Roles not found in the
database will be silently skipped.  Returns a count of how many roles were
actually deleted.


=head2  list_users
(Class method)

    my @users = Class::User::DBI->list_users( $connector );
    foreach my $listed_user ( @users ) {
        my( $userid, $username, $email ) = @{$listed_user};
        print "userid: ($userid).  username: ($username).  email: ($email).\n";
    }

This is a class method.  Pass a valid DBIx::Connector as a parameter. Returns
a list of arrayrefs.  Each anonymous array contains C<userid>, C<username>,
and C<email>.


=head2  configure_db
(Class method)

    Class::User::DBI->configure_db( $connector );

This is a class method.  Pass a valid DBIx::Connector as a parameter.  Builds
a minimal set of database tables in support of the Class::User::DBI.

The tables created will be C<users>, C<user_ips>, and C<user_roles>.


=head1 DEPENDENCIES

This module requires DBIx::Connector, Authen::Passphrase::SaltedSHA512, and
List::MoreUtils. It also requires a database connection.  The test suite will
use DBD::SQLite, but it has also been tested with DBD::mysql.  None of these
dependencies with the exception of List::MoreUtils could be considered
light-weight.  The dependency chain of this module is indicative of the
difficulty in assuring cryptographically strong random salt generation,
reliable SHA2-512 hashing of passphrases, fork-safe database connectivity, and
transactional commits for inserts and updates spanning multiple tables.


=head1 CONFIGURATION AND ENVIRONMENT

The database used will need at least three User-related tables.  In their
simplest form, a minimal recommendation would be:


    TABLE:          users
    COLUMNS:        userid      VARCHAR(24)  NOT NULL DEFAULT ''
                    salt        CHAR(128)    NOT NULL DEFAULT ''
                    password    CHAR(128)    NOT NULL DEFAULT ''
                    ip_required tinyint(1)   NOT NULL DEFAULT '1'
                    username    VARCHAR(40)  DEFAULT NULL
                    email       VARCHAR(320) DEFAULT NULL
    PRIMARY KEY:    userid


    TABLE:          user_ips
    COLUMNS:        userid      VARCHAR(24)  NOT NULL DEFAULT ''
                    ip          INT(10) UNSIGNED NOT NULL DEFAULT '0'
    PRIMARY KEY:    userid, ip


    TABLE:          user_roles
    COLUMNS:        userid      VARCHAR(24) NOT NULL DEFAULT ''
                    role        VARCHAR(40) NOT NULL DEFAULT ''
    PRIMARY KEY:    userid, role

For convenience, a class method has been provided that will auto-generate
the minimal schema within a SQLite or MySQL database.  The SQLite database is
probably only useful for testing, as it lacks many of the security measures
present in web-stack quality databases.  A sample script that would generate
a minimal database could be as simple as this:

    use strict;
    use warnings;
    use DBIx::Connector;
    use Class::User::DBI;

    my( $dsn, $dbuser, $dbpass )
        = (
            'dbi:mysql:database=cudbi_tests,
            'testing_user',
            'testers_pass'
        );

    my $conn = DBIx::Connector->new(
        $dsn,
        $dbuser,
        $dbpass,
        {
            AutoCommit  => 1,
            RaiseError  => 1,
        }

    );

    Class::User::DBI->configure_db( $conn )

    __END__

Within the C<scripts/> directory of this distribution you will find a script
that accepts a database type (mysql or sqlite), database name, database
username, and database password on the command line.  It then opens the given
database and creates the appropriate tables using a variation on the snippet
shown above.  The script is named C<cudbi-configdb>.  Run it once without
any command line parameters to see details on usage.

After creating the database framework, it might be useful to alter the tables
that have been generated by customizing field widths, text encoding, and so on.
It may be advisable to enable UTF8 for the C<userid>, C<email>, C<username>
fields, and  possibly even for the C<role> field.

There is no explicit size requirement for the C<userid>, C<username>, and
C<role> fields.  They could be made wider if it's deemed useful.  Don't be
tempted to reduce the size of the email address field: The best practice of
coding to the standard dictates that the field needs to be 320 characters wide.

The C<salt> and C<password> fields are used to store a 128 hex-digit
representation of the 512 bit salt and 512 bit SHA2 hash of the user's
passphrase.  More digits is not useful, and less won't store the full salt
and hash.


=head1 DIAGNOSTICS

If you find that your particular database engine is not playing nicely with the
SQL from this module, it could be helpful to modify the test script found in
C<t/15-class_tests.t>, within the distribution's directory by providing the
database login credentials for a test database using the same engine that your
application will actually be using.

Currently the test suite tests against a SQLite database since it's such a
lightweight dependency for the testing.  The author also uses this module
with several MySQL databases.  As you're configuring your database, providing
its credentials to C<t/15-class_tests.t> and running the test script will
offer really good diagnostics if some aspect of your database tables proves to
be at odds with what this module needs.

Be advised that the the test suite drops its tables after completion, so be sure
to run C<t/15-class_tests.t> only on a database set up explicitly for testing
purposes.

=head1 INCOMPATIBILITIES

This module has only been tested on MySQL and SQLite database engines.  If you
are successful in using it with other engines, please send me an email detailing
any additional configuration changes you had to make so that I can document
the compatibility, and improve the documentation for the configuration process.

=head1 BUGS AND LIMITATIONS

This module is still in beta testing.  The API of any version number in the
form of 'xxx.yyy_zzz' could still change.  Once the version reaches the form
of 'xxx.yyy', the API may be considered stable.

=head1 AUTHOR


David Oswald, C<< <davido at cpan.org> >>

=head1 BUGS

Please report any bugs or feature requests to
C<bug-class-user-dbi at rt.cpan.org>, or through the web interface at
L<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Class-User-DBI>.  I will be
notified, and then you'll automatically be notified of progress on your bug as
I make changes.




=head1 SUPPORT

You can find documentation for this module with the perldoc command.

    perldoc Class::User::DBI


You can also look for information at:

=over 4

=item * RT: CPAN's request tracker (report bugs here)

L<http://rt.cpan.org/NoAuth/Bugs.html?Dist=Class-User-DBI>

=item * AnnoCPAN: Annotated CPAN documentation

L<http://annocpan.org/dist/Class-User-DBI>

=item * CPAN Ratings

L<http://cpanratings.perl.org/d/Class-User-DBI>

=item * Search CPAN

L<http://search.cpan.org/dist/Class-User-DBI/>

=back


=head1 ACKNOWLEDGEMENTS


=head1 LICENSE AND COPYRIGHT

Copyright 2012 David Oswald.

This program is free software; you can redistribute it and/or modify it
under the terms of either: the GNU General Public License as published
by the Free Software Foundation; or the Artistic License.

See http://dev.perl.org/licenses/ for more information.


=cut

1; # End of Class::User::DBI