DBIx::MyPassword - Store database authentication information in a CSV file
#--> Include the module, letting it search for a password file use DBIx::MyPassword;
#--> Include the module, giving it an explicit file use DBIx::MyPassword qw(/password/file.csv);
#--> Connect to database returning DBI database handle my $dbh = DBIx::Password->connect($user);
#--> Get a list of all available virtual users DBIx::MyPassword->getVirtualUsers();
#--> Check to see if a virtual user exits DBIx::MyPassword->checkVirtualUser($user);
#--> Get the real database user for a virtual user DBIx::MyPassword->getUser($user);
#--> Get the database password for a virtual user DBIx::MyPassword->getPassword($user);
#--> Get the data source information for a virtual user DBIx::MyPassword->getDataSource($user);
#--> Get any database options for a virtual user DBIx::MyPassword->getOptions($user);
This module was largely motivated by DBIx::Password. It is a different take that gives you the ability to keep many different password files. This helps on multi-user machines, where each user can have their own protected password file and still get the benefits of using aliases.
Keeping all of your password information in one place has many benefits. For one, if you have a security policy that forces you to periodically change your database password, you only have to make the change in one place to change it for all of your scripts. Also, with all of your passwords in one spot, you can make sure that the security on your password file is tight.
This module assumes that all of your database connection information is stored in a standard CSV file. This file (or files) can have as many records as you would like. The fields found in each record include:
Currently, there are four places that this module searches for your password file. The order of the search is:
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.
An override of the of the DBI::connect subroutine. This method looks up the specified virtual user and returns a standard DBI connection.
Return a sorted list of virtual users.
Returns true if the specified virtual user exists, false if not.
Return database user for the specified virtual user.
Return password for the specified virtual user.
Return data source information for the specified virtual user.
Return options for the specified virtual user.
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
Josh McAdams, joshua.mcadams at gmail dot com
perl(1); DBI(3); DBIx::Password(3);