view release on metacpan or  search on metacpan

lib/DBIx/MyPassword.pm  view on Meta::CPAN

reference the connection information

=item 2 User 

The database user

=item 3 Password

The password for the database user

=item 5 Data Source

A DBI data source, for instance "dbi:mysql:test"

=item 6 Options

DBI options that will be eval'ed into a hash, for instance 
"RaiseError=>1,PrintError=>1"

=back

=head2 Specifying The Password File Location

Currently, there are four places that this module searches for your password 
file.  The order of the search is:

=over

=item 1 Explicit File Via use

File specified in when 'use'ing the module

=item 2 Explicit File Via Environment 

File specified by the MYPASSWORD environment variable 

=item 3 Current Working Directory

A file named '.mypassword' in the current working directory

=item 4 Home Directory

A file named '.mypassword' in the users home directory, as specified 
by the HOME environment variable

=back

=head2 Securing The Password File

One of the primary reasons that this module was developed was so that I 
could secure my password information in a shared environment.  Here is 
how I do it.  If you see holes in this, please let me know.  Also, I do 
most of my development on some flavor of UNIX, Linux, AIX, etc.  These 
systems are what I know best.  If there is a better (or just plain 
different) way to do security on another system, let me know and I'll 
include it here.

For *X, all that you have to do is change the permissions on your 
password file so that you are the only person who can read it.  A simple:

	chmod 400 .mypassword

is all that it takes.  Each user can have their own password file that 
only they can read.  The caveat of this is that only scripts executed 
by you can read the file too... not sure how that fairs for web 
development.

=head1 SUBROUTINES/METHODS

=head2 connect(virtual_user)

An override of the of the DBI::connect subroutine.  This method looks up 
the specified virtual user and returns a standard DBI connection.

=head2 getVirtualUsers()

Return a sorted list of virtual users.

=head2 checkVirtualUser(virtual_user)

Returns true if the specified virtual user exists, false if not.

=head2 getUser(virtual_user)

Return database user for the specified virtual user.

=head2 getPassword(virtual_user)

Return password for the specified virtual user.

=head2 getDataSource(virtual_user)

Return data source information for the specified virtual user.

=head2 getOptions(virtual_user)

Return options for the specified virtual user.

=head1 INSTALL

Just a standard module install will get the job done.  If you would like, 
you can set the environment variables MP_DBUSER, MP_DBPASS, MP_DBDS, and 
MP_DBOPTS to allow the test scripts to connect to a real database.

	MP_DBUSER -> A real database user name
	MP_DBPASS -> The database user's password
	MP_DBDS   -> A DBI data source, for instance "dbi:mysql:test"
	MP_DBOPTS -> Any DBI connection options, for instance 
                   "RaiseError => 1, PrintError => 1"

Environment variables are not, these are the commands to install:

	perl Makefile.PL
	make
	make test
	make install

=head1 DEPENDENCIES

L<warnings>, L<strict>, L<Carp>, L<DBI>, L<IO::File>, L<Text::CSV>, 
L<File::Spec>