From 17360c6f4511fc9caa56f418d9d21c5cbb510bbf Mon Sep 17 00:00:00 2001 From: tgl Date: Wed, 27 May 2009 22:12:53 +0000 Subject: [PATCH] Improve release note explanation of the change in libpq's handling of default usernames versus Kerberos tickets. Per confusion about what bug #4824 was really about. --- doc/src/sgml/release-8.4.sgml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/release-8.4.sgml b/doc/src/sgml/release-8.4.sgml index 7c193d8f4e..b479259828 100644 --- a/doc/src/sgml/release-8.4.sgml +++ b/doc/src/sgml/release-8.4.sgml @@ -2703,12 +2703,18 @@ - Make Kerberos connections use the same method to determine the - username of the client as all other authentication methods (Magnus) + Do not rely on Kerberos tickets to determine the default database + username (Magnus) - Previously a special Kerberos-only API was used. + Previously, a Kerberos-capable build of libpq would use the + principal name from any available Kerberos ticket as default + database username, even if the connection wasn't using Kerberos + authentication. This was deemed inconsistent and confusing. + The default username is now determined the same way with or + without Kerberos. Note however that the database username must still + match the ticket when Kerberos authentication is used. -- 2.11.4.GIT