Sorry for the long subject but I solved the questions I posted about and
thought I would share my $solution.
The initial problem was:
Right now I have an application set up for multiple clients: clientA,
clientB, clientC.
Each client has their own users.
The way I have it setup is clientA
WAS: A better way to handle multiple client authentication?
Yeah I use something similar in another application, but in this
application I actually need to change the Auth_DBI_data_source variable
since the FROM pwd_table would actually need to be FROM
clientA.pwd_table and I can't see how to
My suggestion would be to subclass AuthDBI to make the constructor
fiddle with the dir_config entries that AuthDBI uses.
See the docs for dir_config (the perl interface to PerlSetVar variables:
http://perl.apache.org/docs/2.0/api/Apache2/ServerUtil.html#C_dir_config_
I have no idea how
