Bug 83780 - sspi / gssapi login from Windows Client to Linux (Samba4) PostgreSQL server
Summary: sspi / gssapi login from Windows Client to Linux (Samba4) PostgreSQL server
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Documentation (show other bugs)
Version:
(earliest affected)
4.3.1.2 release
Hardware: x86-64 (AMD64) All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Help-Changes-Features
  Show dependency treegraph
 
Reported: 2014-09-11 20:41 UTC by Michael J Evans
Modified: 2023-06-12 03:11 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael J Evans 2014-09-11 20:41:53 UTC
Client: A 64 bit Windows 7 host logged in to a domain; LibreOffice 4.3.1.2; native 64 bit PostgreSQL driver has been installed.
Server: (Generic Debian Linux with) PostgreSQL 9.4beta2

Server messages

2014-09-11 20:36:10 UTC [26574-1] michael.evans@postgres LOG:  08006: could not receive data from client: Connection reset by peer
2014-09-11 20:36:10 UTC [26574-2] michael.evans@postgres LOCATION:  pq_recvbuf, pqcomm.c:869
2014-09-11 20:36:10 UTC [26574-3] michael.evans@postgres FATAL:  28000: GSSAPI authentication failed for user "michael.evans"
2014-09-11 20:36:10 UTC [26574-4] michael.evans@postgres DETAIL:  Connection matched pg_hba.conf line 101: "host        all             all             0.0.0.0/0               gss"
2014-09-11 20:36:10 UTC [26574-5] michael.evans@postgres LOCATION:  auth_failed, auth.c:285


Client messages

Couldn't establish database connection to 'sdbc:postgresql:host=EXAMPLE dbname=postgres'
SSPI continuation error: The specified target is unknown or unreachable (80090303)


When on a different Samaba4 AD member than the postgresql server I kinit to the same domain account and connect using psql GSSAPI authentication is successful.

psql -h v-s4 -U michael.evans -d postgres


Additionally, I have not yet been able to locate an official up to date guide for establishing such a connection.  Older versions mention a gsslib connection parameter but that appears to be invalid with this version of LibreOffice/PostgreSQL.
Comment 1 Michael J Evans 2014-09-11 21:28:11 UTC
This should probably be altered to a lower priority additional documentation request.  I decided to try getting pgAdmin III to work in the same environment and a more helpful remark there allowed me to understand the issue.

When using sspi/gssapi the FQDN of the service must be used, not just a hostname that works in the default search domain(s).


host=host.domain.example.com dbname=DBNAME


The username, if left blank, usefully infers your domain login name (prior to the @ part).

DBNAME is whatever database you are connecting to; for testing I was using postgres (the built in informational for database database).
Comment 2 Alex Thurgood 2014-10-21 09:14:07 UTC
Setting to documentation enhancement
Comment 3 Alex Thurgood 2015-01-03 17:39:21 UTC Comment hidden (no-value)
Comment 4 Olivier Hallot 2022-11-12 10:50:50 UTC
given the page

https://help.libreoffice.org/master/en-US/text/sdatabase/dabawiz02pgsql.html?&DbPAR=BASE&System=UNIX

is this issue still valid?
Comment 5 QA Administrators 2023-05-12 03:20:01 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-06-12 03:11:44 UTC
Dear Michael J Evans,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp