> Which is why major DBMSs are increasingly relying on SSO
> based solutions. (e.g., Kerberos/LDAP authentication).
> Not certain if DBI is the proper level to implement that,
> (probably needs to be down at the DBD <=> DBMS level).
> And "in a standard way" may still be wishful thinking.
>
> Also, I'm not sold on the idea that a ~/.dbi file is particularly
> secure in that regard. Not neccesarily opposed, just not convinced
> its the right solution. (I don't like cleartext passwords either,
> but due to the variance in DBMS's authentication methods, I don't know if
> DBI can solve that problem).
Could use an approach like LWP: Stock "authentication" hook
gets called if the remote side asks for authn data,
something like:
{
RaiseError => 1,
AuthnHook => $coderef,
}
would let you cover it however you like.
And/or an automatic redirect via tunnel (basically something
like ssh -L with an ssh module handling the redirect) might
also work.
--
Steven Lembark 85-09 90th Street
Workhorse Computing Woodhaven, NY 11421
[EMAIL PROTECTED] 1 888 359 3508
