Thank you for your suggestion. I arrived at the same suspicion. And that was
it. Reverse DNS was not set up correctly.
Fra: Michael van der Kolff
Sendt: 6. juni 2022 15:50
Til: Niels Jespersen
Cc: pgsql-general list
Emne: Re: GSSAPI authentication
From the tiny bit I know about this, and a
3 PM Niels Jespersen wrote:
>>
>>> *Fra:* Michael van der Kolff
>>> *Sendt:* 6. juni 2022 14:26
>>> *Til:* Niels Jespersen
>>> *Cc:* pgsql-general list
>>> *Emne:* Re: GSSAPI authentication
>>>
>>>
>>>
>>
olff
>> *Sendt:* 6. juni 2022 14:26
>> *Til:* Niels Jespersen
>> *Cc:* pgsql-general list
>> *Emne:* Re: GSSAPI authentication
>>
>>
>>
>> >This sounds like your PG service was unable to authenticate itself to AD.
>>
>> >
>>
>
ell.
--Michael
On Mon, Jun 6, 2022 at 11:33 PM Niels Jespersen wrote:
> *Fra:* Michael van der Kolff
> *Sendt:* 6. juni 2022 14:26
> *Til:* Niels Jespersen
> *Cc:* pgsql-general list
> *Emne:* Re: GSSAPI authentication
>
>
>
> >This sounds like your PG se
Fra: Michael van der Kolff
Sendt: 6. juni 2022 14:26
Til: Niels Jespersen
Cc: pgsql-general list
Emne: Re: GSSAPI authentication
>This sounds like your PG service was unable to authenticate itself to AD.
>
>There's probably a trick to that somewhere - AD doesn't really want
n to server at
>> "srvpostgres4.xxx.local" (172.30.33.30), port 1609 failed: GSSAPI
>> continuation error: Unspecified GSS failure. Minor code may provide more
>> information: Server not found in Kerberos database
>>
>>
>>
>> Server log is like this
&g
s like this
>
>
>
> 2022-06-06 08:14:01.176
> CEST,"yyy","db1",474094,"172.30.32.213:33556",627e83c9.73bee,2,"authentication",2022-06-06
> 08:14:01 CEST,2/14544,0,FATAL,28000,"GSSAPI authentication failed for user
> ""y
83c9.73bee,2,"authentication",2022-06-06
08:14:01 CEST,2/14544,0,FATAL,28000,"GSSAPI authentication failed for user
""yyy""","Connection matched pg_hba.conf line 15: ""hostall all
172.0.0.0/8 gss map=x
Tom,
I wasn't able to get pgadmin4 working with the symlinks, but I'm not very
knowledgeable about libraries.
But that's not a problem. I appreciate everyone diagnosing the issue. I'll
reach out the pgsql-admin forum to see if there's a simple workaround or if
a GSSAPI-enabled pgadmin4 client is
Sean McDaniel writes:
> I followed your suggestions and symlinked libpq.5.dylib under
> /Applications/pgAdmin 4.app/Contents/Frameworks to the homebrew library
> /usr/lib/libpq.5.6.dylib, but unfortunately pgadmin4 now fails on launch
> with the error "The pgadmin4 server could not be contacted."
Thanks Tom and Neil.
What you've said makes sense. The pgadmin4 pibpq doesn't support GSSAPI.
I followed your suggestions and symlinked libpq.5.dylib under
/Applications/pgAdmin 4.app/Contents/Frameworks to the homebrew library
/usr/lib/libpq.5.6.dylib, but unfortunately pgadmin4 now fails on lau
Neil writes:
> On Oct 27, 2020, at 12:23 PM, Tom Lane wrote:
>> A quick look through our source code finds that error string only in
>> libpq; it indicates that libpq was built without GSSAPI support.
> On my Mac pgadmin4 seems to use its own libpq.
> You can find it at: /Applications/pgAdmin\
> On Oct 27, 2020, at 12:23 PM, Tom Lane wrote:
>
> Sean McDaniel writes:
>> I'm using pgadmin4 on a macOS system and I'm having trouble connecting to a
>> server of interest. The "Connect to Server" dialog box has a warning:
>> "GSSAPI au
Sean McDaniel writes:
> I'm using pgadmin4 on a macOS system and I'm having trouble connecting to a
> server of interest. The "Connect to Server" dialog box has a warning:
> "GSSAPI authentication not supported". I cannot proceed beyond that point.
Server" dialog box has a warning:
"GSSAPI authentication not supported". I cannot proceed beyond that point.
It seems to be a GSSAPI issue. I have postgres installed via homebrew and
it supports GSSAPI. I can connect directly to the server using psql (and
pgcli) from the command
15 matches
Mail list logo
