mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Improve release note explanation of the change in libpq's handling of

Browse Source 
default usernames versus Kerberos tickets.  Per confusion about what
bug #4824 was really about.
This commit is contained in:
Tom Lane 2009-05-27 22:12:53 +00:00
parent b1c2781951
commit ee3980ebf3
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/release-8.4.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.4.sgml,v 1.6 2009/05/14 22:17:28 tgl Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.4.sgml,v 1.7 2009/05/27 22:12:53 tgl Exp $ -->
<!-- See header comment in release.sgml about typical markup --> <!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-8-4"> <sect1 id="release-8-4">
@ -2703,12 +2703,18 @@
<listitem> <listitem>
<para> <para>
Make Kerberos connections use the same method to determine the Do not rely on Kerberos tickets to determine the default database
username of the client as all other authentication methods (Magnus) username (Magnus)
</para> </para>
<para> <para>
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.
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>