Re: GSSAPI server side on Linux, SSPI client side on Windows - Mailing list pgsql-general

From Brian Crowell
Subject Re: GSSAPI server side on Linux, SSPI client side on Windows
Date
Msg-id CAAQkdDobA6G8X7xaKtzsLMSiZB3T_6otrGf-pXmfsbdXKz_-mA@mail.gmail.com
Whole thread Raw
In response to Re: GSSAPI server side on Linux, SSPI client side on Windows  (Christian Ullrich <chris@chrullrich.net>)
Responses Re: GSSAPI server side on Linux, SSPI client side on Windows
List pgsql-general
On Mon, Nov 11, 2013 at 11:56 PM, Christian Ullrich
<chris@chrullrich.net> wrote:
>> On Mon, Nov 11, 2013 at 10:51 PM, Brian Crowell <brian@fluggo.com> wrote:
>> * If I don't specify my username, Npgsql sends it in lowercase "bcrowell"
>
> Hmm. That is related one problem I've been having with SSPI auth from libpq/ODBC. The database treats the claimed
username case-sensitively when looking up the user info in pg_authid, and if the user logged on to Windows with a name
differingin case from what the database thinks it is, authentication fails. Npgsql sending it always in lower case is
preciselywhat I landed on as a workaround (basically overriding libpq's automatic user name detection in the ODBC
connectionstring by appending a UID option). 

The message I get in the log is "provided user name
(bcrowell@REALM.COM) and authenticated username (BCrowell@REALM.COM)
do not match," so it looks like I have to teach Npgsql to match
whatever Windows is sending in GSSAPI. That, or teach Postgres how to
lowercase the name on arrival.

What did you do to get around this?

—Brian


pgsql-general by date:

Previous
From: gajendra s v
Date:
Subject: select Xpath is returning values with {}
Next
From: Christian Ullrich
Date:
Subject: Re: GSSAPI server side on Linux, SSPI client side on Windows