Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit786e2f6

Browse files
committed
Clarify documentation about username mapping when authenticating with
GSSAPI or Kerberos.Ian Turner
1 parentde9ec65 commit786e2f6

File tree

1 file changed

+18
-13
lines changed

1 file changed

+18
-13
lines changed

‎doc/src/sgml/client-auth.sgml

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.131 2010/02/03 17:25:05 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.132 2010/02/20 19:21:14 momjian Exp $ -->
22

33
<chapter id="client-authentication">
44
<title>Client Authentication</title>
@@ -824,23 +824,28 @@ omicron bryanh guest1
824824
The following configuration options are supported for <productname>GSSAPI</productname>:
825825
<variablelist>
826826
<varlistentry>
827-
<term><literal>map</literal></term>
827+
<term><literal>include_realm</literal></term>
828828
<listitem>
829829
<para>
830-
Allows for mapping between system and database usernames. See
831-
<xref linkend="auth-username-maps"> for details.
830+
If set to <literal>1</>, the realm name from the authenticated user
831+
principal is included in the system user name that's passed through
832+
username mapping (<xref linkend="auth-username-maps">). This is
833+
useful for handling users from multiple realms.
832834
</para>
833835
</listitem>
834836
</varlistentry>
835837

836838
<varlistentry>
837-
<term><literal>include_realm</literal></term>
839+
<term><literal>map</literal></term>
838840
<listitem>
839841
<para>
840-
If set to <literal>1</>, the realm name from the authenticated user
841-
principal is included in the system user name that's passed through
842-
username mapping (<xref linkend="auth-username-maps">). This is
843-
useful for handling users from multiple realms.
842+
Allows for mapping between system and database usernames. See
843+
<xref linkend="auth-username-maps"> for details. For a Kerboros
844+
principal <literal>username/hostbased@EXAMPLE.COM</literal>, the
845+
username used for mapping is <literal>username/hostbased</literal>
846+
if <literal>include_realm</literal> is disabled, and
847+
<literal>username/hostbased@EXAMPLE.COM</literal> if
848+
<literal>include_realm</literal> is enabled.
844849
</para>
845850
</listitem>
846851
</varlistentry>
@@ -1027,10 +1032,10 @@ omicron bryanh guest1
10271032
<para>
10281033
When connecting to the database make sure you have a ticket for a
10291034
principal matching the requested database user name. For example, for
1030-
database user name <literal>fred</>,bothprincipal
1031-
<literal>fred@EXAMPLE.COM</>and
1032-
<literal>fred/users.example.com@EXAMPLE.COM</> could be used to
1033-
authenticate to the database server.
1035+
database user name <literal>fred</>, principal
1036+
<literal>fred@EXAMPLE.COM</>would be able to connect. To also allow
1037+
principle<literal>fred/users.example.com@EXAMPLE.COM</>, use a username
1038+
map, as described in <xref linkend="auth-username-maps">.
10341039
</para>
10351040

10361041
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp