authenticate - Search results in mailing lists
Mailing lists >> pgsql-hackers >> Thread
2025-04-25 00:52:53 | Re: Making sslrootcert=system work on Windows psql (Jelte Fennema-Nio)
unauthenticated TLS. I believe the only way to fix that is by having a *standard
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (38)
2025-04-21 19:57:33 | Re: [PoC] Federated Authn/z with OAUTHBEARER (Jacob Champion)
authentication scheme for authenticating clients that were issued a client password. We rely on that
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-04-19 02:26:32 | Re: disabled SSL log_like tests (Tom Lane)
authentication failed for user "anotheruser"/, # certificate authentication should be logged even on failure - # temporarily(?) skip
Mailing lists >> pgsql-hackers >> Thread
2025-04-16 03:03:43 | Re: dispchar for oauth_client_secret (Jacob Champion)
authenticate libpq (and by extension, postgres_fdw), not the end user. From the point of view
Mailing lists >> pgsql-hackers >> Thread
2025-04-10 19:00:32 | Re: Capturing both IP address and hostname in the log (Tom Lane)
authentication', and 'authorization'. The empty string disables all connection logging. 'all' enables all available connection
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-03-30 00:29:29 | Re: AIO v2.5 (Noah Misch)
authentication - protocol sync loss, where we'd fail to send a client message - client already
Mailing lists >> pgsql-hackers >> Thread
2025-03-26 09:41:48 | Re: Update LDAP Protocol in fe-connect.c to v3 (Peter Eisentraut)
authentication support in the backend, the other is the connection parameter lookup in libpq. The former
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (25)
2025-03-18 19:53:51 | Re: dblink: Add SCRAM pass-through authentication (Jacob Champion)
authentication happens is only one part -- we have to ensure authentication takes place using the end user
Mailing lists >> pgsql-hackers >> Thread
2025-03-14 20:39:30 | More Perl cleanups (Dagfinn Ilmari Mannsåker)
authenticated:/]); unlink($pgpassfile); -delete $ENV{"PGPASSFILE"}; +delete $ENV{PGPASSFILE}; note "Authentication tests with specific HBA policies
Mailing lists >> pgsql-hackers >> Thread
2025-03-09 00:58:55 | Re: pg16 && GSSAPI && Heimdal/Macos (Todd M. Kover)
authentication, so having a client that supports different things than the server is just fine
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2025-03-06 23:16:20 | Re: Refactoring postmaster's code to cleanup after child exit (Andres Freund)
authentication_timeout" (1 s .. 600 s) I had to increase PG_TEST_TIMEOUT_DEFAULT due to some
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (20)
2025-03-06 17:56:16 | Re: Log connection establishment timings (Bertrand Drouvot)
authenticated" but needs to be log_connections = 'authorized,authenticated' in the postgresql.conf file. That
Mailing lists >> pgsql-hackers >> Thread
2025-03-03 23:48:45 | Re: Flaky 003_start_stop.pl test (Thomas Munro)
authenticated: user="invalid_user" method=trust (/tmp/cirrus-ci-build/build/testrun/postmaster/003_start_stop/data/t_003_start_stop_main_data/pgdata/pg_hba.conf:117) 03:40:42.543 UTC [31690][client backend
Mailing lists >> pgsql-hackers >> Thread
2025-03-03 20:11:55 | Re: PATCH: warn about, and deprecate, clear text passwords (Isaac Morland)
authentication doesn't allow sending cleartext passwords and then relied on the phase-out of MD5 passwords
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-02-25 21:06:18 | Re: Log connection establishment timings (Melanie Plageman)
authentication duration to total connection establishment duration to see how much time was spent on authentication