8.3 problems with sspi authentication

From: "Matthias Mohr" <Matthias(at)Mohrenclan(dot)de>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: 8.3 problems with sspi authentication
Date: 2008-02-21 20:27:20
Message-ID: 007d01c874c8$2a734de0$8200a8c0@mohr.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi everybody,

this is my first post here, so I don't know if this has already be discussed here.

I tried to use the new sspi authentication in PostgreSQL 8.3 to directly use a Windows user for PostgreSQL authentication.
So for a test I changed the default "127.0.01/32" line in pg_hba.conf from "md5" to "sspi" and tried to restart the service.

The restart of the service failed and I found the following lines (multiple times) in my logs:
---------------------------------------------------------------------------------------------------------------------------------------
2008-02-21 21:17:21 CET LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2008-02-21 21:17:21 CET FATAL: SSPI authentication failed for user "postgres"
---------------------------------------------------------------------------------------------------------------------------------------

Then I tried to additionally add the sspi line to the pg_hba.conf.
Now the services immediately fails to start and the only additional line in the log is:
---------------------------------------------------------------------------------------------------------------------------------------
2008-02-21 21:19:17 CET LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
---------------------------------------------------------------------------------------------------------------------------------------
No failure, only one of the above line.

Am I doing something wrong or is this a (known) bug?

I'm using Windows XP Professional with SP2 and a lot of additional Microsoft fixes.
I installed PostgreSQL with the Windows installer.
My computer is not part of any Domain or Active Directory...

Any suggestions (or helpful hints how I can find out, what's going wrong)?

with regards,
Matthias

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Vincent D'Haene 2008-02-21 20:53:42 Re: BUG #3951: SELECT ... WHERE Param = ? does not work if Param is of type bytea
Previous Message Andy Satori 2008-02-21 20:24:11 BUG #3978: plperl configure / build process behavior wrt Universal Binaries