Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1miep4-0004J3-6U for pgsql-odbc@arkaria.postgresql.org; Thu, 04 Nov 2021 15:38:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1miep2-00084h-Gg for pgsql-odbc@arkaria.postgresql.org; Thu, 04 Nov 2021 15:38:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mieIr-0006By-HJ for pgsql-odbc@lists.postgresql.org; Thu, 04 Nov 2021 15:05:21 +0000 Received: from mailout113.bayern.de ([195.200.70.113]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mieIo-00050J-C4 for pgsql-odbc@postgresql.org; Thu, 04 Nov 2021 15:05:20 +0000 Received: from post25.bybn.de ([10.197.20.25]) by mailout113.bayern.de (8.15.2/8.15.2) with ESMTP id 1A4F5EMN032412 for ; Thu, 4 Nov 2021 16:05:14 +0100 Received: from ZMX-EXP4-P17741.max.bayern.de (ZMX-EXP4-P17741.max.bayern.de [10.173.241.167]) by post25.bybn.de (8.14.4/8.14.4) with ESMTP id 1A4F58B8034634 for ; Thu, 4 Nov 2021 16:05:14 +0100 (envelope-from Franz-Josef.Faerber@stmuk.bayern.de) Received: from ZMX-EXPB-P17750.max.bayern.de (10.173.241.172) by ZMX-EXP4-P17741.max.bayern.de (10.173.241.167) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.15; Thu, 4 Nov 2021 16:05:13 +0100 Received: from ZMX-EXPB-P17750.max.bayern.de (10.173.241.172) by ZMX-EXPB-P17750.max.bayern.de (10.173.241.172) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.15; Thu, 4 Nov 2021 16:05:13 +0100 Received: from ZMX-EXPB-P17750.max.bayern.de ([10.173.241.172]) by ZMX-EXPB-P17750.max.bayern.de ([10.173.241.172]) with mapi id 15.01.2308.015; Thu, 4 Nov 2021 16:05:13 +0100 From: =?iso-8859-1?Q?F=E4rber=2C_Franz-Josef_=28StMUK=29?= To: "pgsql-odbc@postgresql.org" Subject: send current username with gssapi Thread-Topic: send current username with gssapi Thread-Index: AdfRjIaU9w/qbNSlSei3PlnXFs4bcw== Date: Thu, 4 Nov 2021 15:05:13 +0000 Message-ID: <5db9aac12b154a6b8ba21df37fc31125@stmuk.bayern.de> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.171.82.81] Content-Type: multipart/alternative; boundary="_000_5db9aac12b154a6b8ba21df37fc31125stmukbayernde_" MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_5db9aac12b154a6b8ba21df37fc31125stmukbayernde_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I am using psqlODBC from Windows machines to connect to a GSSAPI-enabled Po= stgreSQL-Server on a linux machine. Passwordless Login works when I specify the current windows user's samaccou= ntname, and no password. However, the use case is I am connecting postgres tables into 3rd party sof= tware, which will store the current user's samaccountname with the connecti= on string. When the next user opens the database, he has to type in his (di= fferent) username... and so on every time another user opens the file. Does psqlODBC have a feature like Npgsql's "Integrated Security=3Dtrue" to = automagically send the current user's samaccountname as username? Regards, Franz-Josef F=E4rber --_000_5db9aac12b154a6b8ba21df37fc31125stmukbayernde_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello,

 

I am using psqlODBC from Windows machines to connect= to a GSSAPI-enabled PostgreSQL-Server on a linux machine.

 

Passwordless Login works when I specify the current = windows user’s samaccountname, and no password.

 

However, the use case is I am connecting postgres ta= bles into 3rd party software, which will store the current user’s sam= accountname with the connection string. When the next user opens the databa= se, he has to type in his (different) username… and so on every time another user opens the file.

 

Does psqlODBC have a feature like Npgsql’s = 222;Integrated Security=3Dtrue“ to automagically se= nd the current user’s samaccountname as username?

 

 

Regards,

Franz-Josef F=E4rber

 

--_000_5db9aac12b154a6b8ba21df37fc31125stmukbayernde_--