() in npgsql and libpq do the same thing though.
Regards, Reto
2010/12/22 Brar Piening
> Original Message
> Subject: Re: [GENERAL] "could not accept SSPI security context"
> From: Reto Schöning
> To: Brar Piening
> Date: 22.12.2010 17:08
>
>
&g
other words - I'd be willing to overhaul the wohle thing if I find a
> good reason to do so (and some time).
>
> Regards,
>
> Brar
>
>
> On Fri, 3 Dec 2010 06:32:17 +0100, Reto Schöning
> wrote:
>
> thanks, and sorry for my slow responses, I'm bogg
. From the
docs I understand that with SSPI, pg should try kerberos first and fall back
to NTLM. This works when connecting from psql. Maybe Npgsql goes straight
for NTLM, at least when using it the way I do?
2010/11/29 Reto Schöning
> thanks a lot for the hints.
>
> client side log
thanks a lot for the hints.
client side logging: the user name corresponds to the expected user, without
the domain prefix ("rsc"). See the full log output below.
security event log: I should get that shortly from our IT.
Regards, Reto
29.11.2010 10:37:17 4412 Debug Entering
NpgsqlConnection.Npg
; On Mon, Nov 22, 2010 at 11:57, Reto Schöning
> wrote:
> > Thanks for the hint. The full error message from npgsql including that
> > detail row is
> > Npgsql.NpgsqlException was unhandled
> > Message="FATAL: XX000: could not accept SSPI security cont
Hi,
I've set up 8.3 to use SSPI for authentication (clients and server on
windows XP). I can successfully connect from clients using psql and another
db client using SSPI authentication. However when trying to connect with
Npgsql (2.0.11) as the same user, the following error occurs:
"could no
