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 CAAQkdDqYiQOfEzb5M4fh054MWhEY77rdLnOAgY2QdS5+QZt-YA@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 Tue, Nov 5, 2013 at 11:35 AM, Christian Ullrich <chris@chrullrich.net> wrote:
> Hence my suspicion that it doesn't. I did not have the time to compare every
> function call yet.

It doesn't. But it's a pretty close match; it looks like it was ported
directly from the libpq code. libpq actually uses the same code path
for SSPI and GSSAPI on Windows, with a boolean to switch a few things
between the two. I've been trying to duplicate those changes in
Npgsql.

I think I'm getting closer though. I have psql on Windows successfully
authenticating, so I can't be too far off.


> The GSSAPI error messages are of the usual helpful kind, even including the
> colon that is followed by no detail.

I've been trying to enable the KRB5_TRACE environment variable in the
Postgres child processes, but I can't seem to make it stick. That
would (should!) provide some sort of help.

—Brian


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres 9.3.1 and Self Test Failure "pg_regress: no *.source files found"
Next
From: Brian Crowell
Date:
Subject: Re: GSSAPI server side on Linux, SSPI client side on Windows