pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedODBC authentication failure
4+ messages / 3 participants
[nested] [flat]
* ODBC authentication failure
@ 1999-02-14 19:04 Ken J. Wright <ken@cncware.com>
0 siblings, 0 replies; 4+ messages in thread
From: Ken J. Wright @ 1999-02-14 19:04 UTC (permalink / raw)
To: pgsql-interfaces
Hello Byron,
Attached is the tracelog from an attempted ODBC connect.
This occurs whenever authentication fails during an attempt to connect
(using ODBCExpress). I believe I should get a connection dialog, but it
fails instead. I have tried different hdbc prompt settings & also different
pg_hba.conf settings, but basically the same thing happens whenever
authentication fails for any reason. The trace indicates that this is
another ODBC2.0 vs. ODBC3.0 issue. Would you agree? And more importantly,
how do I, you, we fix it? I can certainly (and do currently) just trap the
error and deal with it through my own dialog box, but I was hoping to also
be able to rely on the fallback of the driver handling the prompting.
Comments?
Cheers!
Ken
Attachments:
sql.log (text/plain, 5.0K) download
gl ffc013a5:ffc0e0bd ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0121fc5c
SQLHANDLE * 0x0164164c
gl ffc013a5:ffc0e0bd EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0121fc5c
SQLHANDLE * 0x0164164c ( 0x0121ff10)
gl ffc013a5:ffc0e0bd ENTER SQLGetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eedd4
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd EXIT SQLGetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eedd4
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd ENTER SQLSetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x00000000
SQLINTEGER 4
gl ffc013a5:ffc0e0bd EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x00000000
SQLINTEGER 4
gl ffc013a5:ffc0e0bd ENTER SQLGetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eede0
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd EXIT SQLGetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eede0
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd ENTER SQLDriverConnectW
HDBC 0x0121ff10
HWND 0x00000b70
WCHAR * 0x6a9ae068 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x6a9ae068
SWORD 8
SWORD * 0x00000000
UWORD 3 <SQL_DRIVER_COMPLETE_REQUIRED>
gl ffc013a5:ffc0e0bd EXIT SQLDriverConnectW with return code -1 (SQL_ERROR)
HDBC 0x0121ff10
HWND 0x00000b70
WCHAR * 0x6a9ae068 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x6a9ae068
SWORD 8
SWORD * 0x00000000
UWORD 3 <SQL_DRIVER_COMPLETE_REQUIRED>
DIAG [28000] User authentication failed (210)
DIAG [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr). (0)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 1
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 1
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8 (210)
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6 (26)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 2
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 2
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8 (0)
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6 (140)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 3
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 100 (SQL_NO_DATA_FOUND)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 3
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
* ODBC authentication failure
@ 1999-02-14 19:56 Ken J. Wright <ken@ori-ind.com>
0 siblings, 1 reply; 4+ messages in thread
From: Ken J. Wright @ 1999-02-14 19:56 UTC (permalink / raw)
To: pgsql-interfaces
Hello Byron,
Attached is the tracelog from an attempted ODBC connect.
This occurs whenever authentication fails during an attempt to connect
(using ODBCExpress). I believe I should get a connection dialog, but it
fails instead. I have tried different hdbc prompt settings & also different
pg_hba.conf settings, but basically the same thing happens whenever
authentication fails for any reason. The trace indicates that this is
another ODBC2.0 vs. ODBC3.0 issue. Would you agree? And more importantly,
how do I, you, we fix it? I can certainly (and do currently) just trap the
error and deal with it through my own dialog box, but I was hoping to also
be able to rely on the fallback of the driver handling the prompting.
Comments?
Cheers!
Ken
Attachments:
sql.log (text/plain, 5.0K) download
gl ffc013a5:ffc0e0bd ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0121fc5c
SQLHANDLE * 0x0164164c
gl ffc013a5:ffc0e0bd EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0121fc5c
SQLHANDLE * 0x0164164c ( 0x0121ff10)
gl ffc013a5:ffc0e0bd ENTER SQLGetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eedd4
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd EXIT SQLGetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eedd4
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd ENTER SQLSetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x00000000
SQLINTEGER 4
gl ffc013a5:ffc0e0bd EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x00000000
SQLINTEGER 4
gl ffc013a5:ffc0e0bd ENTER SQLGetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eede0
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd EXIT SQLGetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eede0
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd ENTER SQLDriverConnectW
HDBC 0x0121ff10
HWND 0x00000b70
WCHAR * 0x6a9ae068 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x6a9ae068
SWORD 8
SWORD * 0x00000000
UWORD 3 <SQL_DRIVER_COMPLETE_REQUIRED>
gl ffc013a5:ffc0e0bd EXIT SQLDriverConnectW with return code -1 (SQL_ERROR)
HDBC 0x0121ff10
HWND 0x00000b70
WCHAR * 0x6a9ae068 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x6a9ae068
SWORD 8
SWORD * 0x00000000
UWORD 3 <SQL_DRIVER_COMPLETE_REQUIRED>
DIAG [28000] User authentication failed (210)
DIAG [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr). (0)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 1
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 1
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8 (210)
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6 (26)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 2
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 2
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8 (0)
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6 (140)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 3
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 100 (SQL_NO_DATA_FOUND)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 3
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
* Re: [INTERFACES] ODBC authentication failure
@ 1999-02-19 16:12 Byron Nikolaidis <byronn@insightdist.com>
parent: Ken J. Wright <ken@ori-ind.com>
0 siblings, 0 replies; 4+ messages in thread
From: Byron Nikolaidis @ 1999-02-19 16:12 UTC (permalink / raw)
To: Ken J. Wright <ken@ori-ind.com>; +Cc: pgsql-interfaces
Ken J. Wright wrote:
> Hello Byron,
>
> Attached is the tracelog from an attempted ODBC connect.
> This occurs whenever authentication fails during an attempt to connect
> (using ODBCExpress). I believe I should get a connection dialog, but it
> fails instead. I have tried different hdbc prompt settings & also different
> pg_hba.conf settings, but basically the same thing happens whenever
> authentication fails for any reason. The trace indicates that this is
> another ODBC2.0 vs. ODBC3.0 issue. Would you agree? And more importantly,
> how do I, you, we fix it? I can certainly (and do currently) just trap the
> error and deal with it through my own dialog box, but I was hoping to also
> be able to rely on the fallback of the driver handling the prompting.
> Comments?
>
Looking at the log, I see what you mean about the odbc behavior stuff. But,
when a connect attempt fails, if its because the connection could not be
physically made OR the authentication is wrong, the driver will return an error
from SQLDriverConnect. So it seems to working as designed, even with the
warning message in the log.
The only time the driver will prompt the user is if a password is required to
connect, and one was not provided.
In order to do what you say, I would need to examine the error message that
comes back. If its an authentication related problem, then prompt the user
with a dialog box.
Byron
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [INTERFACES] ODBC authentication failure
@ 1999-02-19 18:16 Ken J. Wright <ken@ori-ind.com>
0 siblings, 0 replies; 4+ messages in thread
From: Ken J. Wright @ 1999-02-19 18:16 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
At 11:12 AM 2/19/99 -0500, you wrote:
>
>
>Ken J. Wright wrote:
>
>> Hello Byron,
>>
>> Attached is the tracelog from an attempted ODBC connect.
>> This occurs whenever authentication fails during an attempt to connect
>> (using ODBCExpress). I believe I should get a connection dialog, but it
>> fails instead. I have tried different hdbc prompt settings & also different
>> pg_hba.conf settings, but basically the same thing happens whenever
>> authentication fails for any reason. The trace indicates that this is
>> another ODBC2.0 vs. ODBC3.0 issue. Would you agree? And more importantly,
>> how do I, you, we fix it? I can certainly (and do currently) just trap the
>> error and deal with it through my own dialog box, but I was hoping to also
>> be able to rely on the fallback of the driver handling the prompting.
>> Comments?
>>
>
>Looking at the log, I see what you mean about the odbc behavior stuff. But,
>when a connect attempt fails, if its because the connection could not be
>physically made OR the authentication is wrong, the driver will return an
error
>from SQLDriverConnect. So it seems to working as designed, even with the
>warning message in the log.
That warning message is what threw up the red flag.
>The only time the driver will prompt the user is if a password is required to
>connect, and one was not provided.
Ok. You are referring to as required by the SQlDriverConnect setting?
>In order to do what you say, I would need to examine the error message that
>comes back. If its an authentication related problem, then prompt the user
>with a dialog box.
Probably very low priority in the scope of things. Maybe best left alone,
as every app has it's own flavor of login dialog anyway. The driver dialog
is more suited to datasource maintenance and can be a bit confusing to a
*normal* user.
Thanks,
Ken
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~1999-02-19 18:16 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-02-14 19:04 ODBC authentication failure Ken J. Wright <ken@cncware.com>
1999-02-14 19:56 ODBC authentication failure Ken J. Wright <ken@ori-ind.com>
1999-02-19 16:12 ` Byron Nikolaidis <byronn@insightdist.com>
1999-02-19 18:16 Re: [INTERFACES] ODBC authentication failure Ken J. Wright <ken@ori-ind.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox