Re: How come drongo didn't fail authentication here? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: How come drongo didn't fail authentication here?
Date
Msg-id 073260f1-e1a1-d4c4-5c99-73c10d35c09f@dunslane.net
Whole thread Raw
In response to How come drongo didn't fail authentication here?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: How come drongo didn't fail authentication here?
List pgsql-hackers
On 2022-07-28 Th 10:24, Tom Lane wrote:
> In commits 7c34555f8/e1bd4990b, I added a new role used by a TAP
> script but neglected the auth_extra incantation needed to allow
> login as that role.  This should have resulted in SSPI auth
> failures on certain Windows configurations, and indeed it did
> on drongo's next run in the v15 branch:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2022-07-27%2022%3A01%3A47
>
> However, its immediately-following run on HEAD succeeded,
> though I'd obviously not had time to put in the fix yet:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2022-07-27%2022%3A30%3A27
>
> How can that be?  Have we somehow broken SSPI authentication
> in HEAD?
>
>             


Nothing is broken. On HEAD drongo uses Unix sockets.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: replacing role-level NOINHERIT with a grant-level option
Next
From: Tom Lane
Date:
Subject: Re: How come drongo didn't fail authentication here?