Joshua D. Drake j...@commandprompt.com writes:
On Fri, 2009-05-22 at 15:24 -0400, Tom Lane wrote:
There's no way we could implement that without a protocol change,
and it doesn't seem worth it to me. The idea that the client gets
to choose seems like a bad idea from a security standpoint
I've asked a few people at pgcon2009 about the issue of connecting users
differently: some in SSIS mode, some - with password. This is still an
issue: if server is configured for SSIS, there is no way to connect with
password. It appears that the solution of the issue is to introduce
connection
Konstantin Izmailov kizmai...@gmail.com writes:
I've asked a few people at pgcon2009 about the issue of connecting users
differently: some in SSIS mode, some - with password. This is still an
issue: if server is configured for SSIS, there is no way to connect with
password.
Huh? The server
Tom Lane wrote:
Konstantin Izmailov kizmai...@gmail.com writes:
I've asked a few people at pgcon2009 about the issue of connecting users
differently: some in SSIS mode, some - with password. This is still an
issue: if server is configured for SSIS, there is no way to connect with
password.
Magnus Hagander mag...@hagander.net writes:
In his scenario, different clients connecting from the same subnet (so
they can't use different pg_hba lines) need to use different
authentication methods. (IIRC, this is an environment coming from
Microsoft SQL Server which does support this)
On Fri, 2009-05-22 at 15:24 -0400, Tom Lane wrote:
I think what he's asking for is the ability for a line in the server to
allow multiple authentication methods, and then for the client to be
able to specify which one of these it uses.
There's no way we could implement that without a
Yes, it is correct. Issue appers not significant at first glance.
However, if you take into account users who are trying to migrate
their apps from MSSQL or Oracle and not willing to rewrite their apps
(relying on the OLEDB driver), you discover that it is not that small
issue. The driver
