From: | Christian Ullrich <chris(at)chrullrich(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: GSSAPI server side on Linux, SSPI client side on Windows |
Date: | 2013-11-05 16:35:15 |
Message-ID: | l5b6np$78h$1@ger.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Stephen Frost wrote:
> * Brian Crowell (brian(at)fluggo(dot)com) wrote:
>> However, the eventual goal was to connect to this same server from a
>> .NET app running on Windows, and here I've run into a snag. The Npgsql
>> library does not support GSSAPI—it only supports SSPI, which is
>> nearly-but-not-enough-like the same thing to count in this situation,
>
> Uhhh, why not?
Because the server on Linux sends AUTH_REQ_GSS, which Npgsql does not
recognize.
I tried to fix it using the reverse of they one-line fix that worked in
both JDBC and libpq. There, the problem was that they only supported
GSSAPI and had no clue about SSPI (except libpq on Windows). The fix was
to basically declare GSSAPI and SSPI to be the same. It didn't work.
In Npgsql's case, the problem is the other way around -- it only knows
SSPI. While making GSSAPI the same as SSPI should work in principle,
there must be some difference somewhere.
--
Christian
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-11-05 16:59:06 | Re: GSSAPI server side on Linux, SSPI client side on Windows |
Previous Message | Merlin Moncure | 2013-11-05 15:51:47 | Re: json datatype and table bloat? |