From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Ludek Finstrle" <luf(at)pzkagis(dot)cz>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: libpq and auth type |
Date: | 2006-01-11 18:25:29 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C7E6A@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
> > It's impossible by definition to know whether a password is
> required
> > until you have the host, user, and database names, since
> the server's
>
> User could be specified another way (e.g. kerberos auth
> doesn't need to specify user parameter). It's the biggest problem.
You need the username in the end, when you make the connection. Libpq
makes this work by picking up the logged in user in the OS if nothing is
specified.
Kerberos only requires that the specified username is identical to that
used to log in to the system. (Actually, that's only true for Microsoft
Kerberos. On unix kerberos, you can specify a different username in some
scenarios)
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Torsten Mager | 2006-01-12 13:53:53 | [libpq] Password authentication failed for user |
Previous Message | Ludek Finstrle | 2006-01-11 16:33:21 | Re: libpq and auth type |