[ psqlodbc-Bugs-1000519 ] Does not pick up default username

Bugs item #1000519, was opened at 2006-01-05 12:53
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=10005 19&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Magnus Hagander (mha)
Assigned to: Nobody (None)
Summary: Does not pick up default username

Initial Comment:
To use ODBC with Kerberos authentication, the connection needs to pick up the current username from the logged in user and use that for authentication. For normal libpq connections, this works fine if you just skip specifying the username completely. For ODBC connection, it crashes. Example vbscript:

set conn = CreateObject("ADODB.Connection")
conn.Open "Driver={PostgreSQL UNICODE};DATABASE=admin;SERVER=server.domain.se"

This gives me the error:
H:\t2.vbs(2, 1) Microsoft OLE DB Provider for ODBC Drivers: Operation was canceled.


If I specify the username (mha) with "uid=mha", it works.


A workaround is possible when connectingl ike above, because I can have my vbscript determine the userid and pass it along. But it's not possible with software using a global DSN that expect integrated login to work the same way as for SQLServer.

------------------------------------------------------------ ----------

>Comment By: Magnus Hagander (mha)
Date: 2006-01-07 18:48

Message:
I think you should be able to reproduce the same problem
when using trust authentication. Just make sure you never
specify a username in the script connecting.

Log file for a run is attached. In order to enable logging,
I created a DSN called "pgtest" with:
data source: pgtest
description:
database: postgres
sslmode: prefer
server: my.server.domain
port: 5432
user name:
password:

All other options are per default.




------------------------------------------------------------ ----------

Comment By: Ludek Finstrle (luf)
Date: 2006-01-05 20:41

Message:
I have no kerberos here. So I can't reproduce the problem.
I need you attach mylog output for unsuccessful login.

------------------------------------------------------------ ----------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=10005 19&group_id=1000125

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org