Baoding-FenShuaJiang
/
Green_GoodERP18_FSJ_Standard
Vērot 1
Pievienot zvaigznīti 0
Vikivietne 捐赠
gooderp18绿色标准版
Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
Koks: 0f75e31513
Atzari Tagi
${ item.name }
Izveidot atzaru ${ searchTerm }
no '0f75e31513'
${ noResults }
Green_GoodERP18_FSJ_Standard/PostgreSQL/doc/postgresql/html/auth-pg-hba-conf.html

471 rinda
36KB
Neapstrādāts Vainot Vēsture 

  1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>

  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.1. The pg_hba.conf File</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="prev" href="client-authentication.html" title="Chapter 20. Client Authentication" /><link rel="next" href="auth-username-maps.html" title="20.2. User Name Maps" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">20.1. The <code xmlns="http://www.w3.org/1999/xhtml" class="filename">pg_hba.conf</code> File</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="client-authentication.html" title="Chapter 20. Client Authentication">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="client-authentication.html" title="Chapter 20. Client Authentication">Up</a></td><th width="60%" align="center">Chapter 20. Client Authentication</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 12.4 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="auth-username-maps.html" title="20.2. User Name Maps">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="AUTH-PG-HBA-CONF"><div class="titlepage"><div><div><h2 class="title" style="clear: both">20.1. The <code class="filename">pg_hba.conf</code> File</h2></div></div></div><a id="id-1.6.7.8.2" class="indexterm"></a><p>

  3.    Client authentication is controlled by a configuration file,

  4.    which traditionally is named

  5.    <code class="filename">pg_hba.conf</code> and is stored in the database

  6.    cluster's data directory.

  7.    (<acronym class="acronym">HBA</acronym> stands for host-based authentication.) A default

  8.    <code class="filename">pg_hba.conf</code> file is installed when the data

  9.    directory is initialized by <code class="command">initdb</code>.  It is

  10.    possible to place the authentication configuration file elsewhere,

  11.    however; see the <a class="xref" href="runtime-config-file-locations.html#GUC-HBA-FILE">hba_file</a> configuration parameter.

  12.   </p><p>

  13.    The general format of the <code class="filename">pg_hba.conf</code> file is

  14.    a set of records, one per line. Blank lines are ignored, as is any

  15.    text after the <code class="literal">#</code> comment character.

  16.    Records cannot be continued across lines.

  17.    A record is made

  18.    up of a number of fields which are separated by spaces and/or tabs.

  19.    Fields can contain white space if the field value is double-quoted.

  20.    Quoting one of the keywords in a database, user, or address field (e.g.,

  21.    <code class="literal">all</code> or <code class="literal">replication</code>) makes the word lose its special

  22.    meaning, and just match a database, user, or host with that name.

  23.   </p><p>

  24.    Each record specifies a connection type, a client IP address range

  25.    (if relevant for the connection type), a database name, a user name,

  26.    and the authentication method to be used for connections matching

  27.    these parameters. The first record with a matching connection type,

  28.    client address, requested database, and user name is used to perform

  29.    authentication. There is no <span class="quote">“<span class="quote">fall-through</span>”</span> or

  30.    <span class="quote">“<span class="quote">backup</span>”</span>: if one record is chosen and the authentication

  31.    fails, subsequent records are not considered. If no record matches,

  32.    access is denied.

  33.   </p><p>

  34.    A record can have several formats:

  35. </p><pre class="synopsis">

  36. local         <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>auth-method</code></em> [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  37. host          <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>address</code></em>     <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  38. hostssl       <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>address</code></em>     <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  39. hostnossl     <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>address</code></em>     <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  40. hostgssenc    <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>address</code></em>     <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  41. hostnogssenc  <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>address</code></em>     <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  42. host          <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>IP-address</code></em>  <em class="replaceable"><code>IP-mask</code></em>      <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  43. hostssl       <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>IP-address</code></em>  <em class="replaceable"><code>IP-mask</code></em>      <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  44. hostnossl     <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>IP-address</code></em>  <em class="replaceable"><code>IP-mask</code></em>      <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  45. hostgssenc    <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>IP-address</code></em>  <em class="replaceable"><code>IP-mask</code></em>      <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  46. hostnogssenc  <em class="replaceable"><code>database</code></em>  <em class="replaceable"><code>user</code></em>  <em class="replaceable"><code>IP-address</code></em>  <em class="replaceable"><code>IP-mask</code></em>      <em class="replaceable"><code>auth-method</code></em>  [<span class="optional"><em class="replaceable"><code>auth-options</code></em></span>]

  47. </pre><p>

  48.    The meaning of the fields is as follows:

  49. 

  50.    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="literal">local</code></span></dt><dd><p>

  51.        This record matches connection attempts using Unix-domain

  52.        sockets.  Without a record of this type, Unix-domain socket

  53.        connections are disallowed.

  54.       </p></dd><dt><span class="term"><code class="literal">host</code></span></dt><dd><p>

  55.        This record matches connection attempts made using TCP/IP.

  56.        <code class="literal">host</code> records match

  57.        <acronym class="acronym">SSL</acronym> or non-<acronym class="acronym">SSL</acronym> connection

  58.        attempts as well as <acronym class="acronym">GSSAPI</acronym> encrypted or

  59.        non-<acronym class="acronym">GSSAPI</acronym> encrypted connection attempts.

  60.       </p><div class="note"><h3 class="title">Note</h3><p>

  61.        Remote TCP/IP connections will not be possible unless

  62.        the server is started with an appropriate value for the

  63.        <a class="xref" href="runtime-config-connection.html#GUC-LISTEN-ADDRESSES">listen_addresses</a> configuration parameter,

  64.        since the default behavior is to listen for TCP/IP connections

  65.        only on the local loopback address <code class="literal">localhost</code>.

  66.       </p></div></dd><dt><span class="term"><code class="literal">hostssl</code></span></dt><dd><p>

  67.        This record matches connection attempts made using TCP/IP,

  68.        but only when the connection is made with <acronym class="acronym">SSL</acronym>

  69.        encryption.

  70.       </p><p>

  71.        To make use of this option the server must be built with

  72.        <acronym class="acronym">SSL</acronym> support. Furthermore,

  73.        <acronym class="acronym">SSL</acronym> must be enabled

  74.        by setting the <a class="xref" href="runtime-config-connection.html#GUC-SSL">ssl</a> configuration parameter (see

  75.        <a class="xref" href="ssl-tcp.html" title="18.9. Secure TCP/IP Connections with SSL">Section 18.9</a> for more information).

  76.        Otherwise, the <code class="literal">hostssl</code> record is ignored except for

  77.        logging a warning that it cannot match any connections.

  78.       </p></dd><dt><span class="term"><code class="literal">hostnossl</code></span></dt><dd><p>

  79.        This record type has the opposite behavior of <code class="literal">hostssl</code>;

  80.        it only matches connection attempts made over

  81.        TCP/IP that do not use <acronym class="acronym">SSL</acronym>.

  82.       </p></dd><dt><span class="term"><code class="literal">hostgssenc</code></span></dt><dd><p>

  83.        This record matches connection attempts made using TCP/IP,

  84.        but only when the connection is made with <acronym class="acronym">GSSAPI</acronym>

  85.        encryption.

  86.       </p><p>

  87.        To make use of this option the server must be built with

  88.        <acronym class="acronym">GSSAPI</acronym> support.  Otherwise,

  89.        the <code class="literal">hostgssenc</code> record is ignored except for logging

  90.        a warning that it cannot match any connections.

  91.       </p><p>

  92.         Note that the only supported

  93.         <a class="link" href="auth-methods.html" title="20.3. Authentication Methods">authentication methods</a> for use

  94.         with <acronym class="acronym">GSSAPI</acronym> encryption

  95.         are <code class="literal">gss</code>, <code class="literal">reject</code>,

  96.         and <code class="literal">trust</code>.

  97.       </p></dd><dt><span class="term"><code class="literal">hostnogssenc</code></span></dt><dd><p>

  98.        This record type has the opposite behavior of <code class="literal">hostgssenc</code>;

  99.        it only matches connection attempts made over

  100.        TCP/IP that do not use <acronym class="acronym">GSSAPI</acronym> encryption.

  101.       </p></dd><dt><span class="term"><em class="replaceable"><code>database</code></em></span></dt><dd><p>

  102.        Specifies which database name(s) this record matches.  The value

  103.        <code class="literal">all</code> specifies that it matches all databases.

  104.        The value <code class="literal">sameuser</code> specifies that the record

  105.        matches if the requested database has the same name as the

  106.        requested user.  The value <code class="literal">samerole</code> specifies that

  107.        the requested user must be a member of the role with the same

  108.        name as the requested database.  (<code class="literal">samegroup</code> is an

  109.        obsolete but still accepted spelling of <code class="literal">samerole</code>.)

  110.        Superusers are not considered to be members of a role for the

  111.        purposes of <code class="literal">samerole</code> unless they are explicitly

  112.        members of the role, directly or indirectly, and not just by

  113.        virtue of being a superuser.

  114.        The value <code class="literal">replication</code> specifies that the record

  115.        matches if a physical replication connection is requested (note that

  116.        replication connections do not specify any particular database).

  117.        Otherwise, this is the name of

  118.        a specific <span class="productname">PostgreSQL</span> database.

  119.        Multiple database names can be supplied by separating them with

  120.        commas.  A separate file containing database names can be specified by

  121.        preceding the file name with <code class="literal">@</code>.

  122.       </p></dd><dt><span class="term"><em class="replaceable"><code>user</code></em></span></dt><dd><p>

  123.        Specifies which database user name(s) this record

  124.        matches. The value <code class="literal">all</code> specifies that it

  125.        matches all users.  Otherwise, this is either the name of a specific

  126.        database user, or a group name preceded by <code class="literal">+</code>.

  127.        (Recall that there is no real distinction between users and groups

  128.        in <span class="productname">PostgreSQL</span>; a <code class="literal">+</code> mark really means

  129.        <span class="quote">“<span class="quote">match any of the roles that are directly or indirectly members

  130.        of this role</span>”</span>, while a name without a <code class="literal">+</code> mark matches

  131.        only that specific role.) For this purpose, a superuser is only

  132.        considered to be a member of a role if they are explicitly a member

  133.        of the role, directly or indirectly, and not just by virtue of

  134.        being a superuser.

  135.        Multiple user names can be supplied by separating them with commas.

  136.        A separate file containing user names can be specified by preceding the

  137.        file name with <code class="literal">@</code>.

  138.       </p></dd><dt><span class="term"><em class="replaceable"><code>address</code></em></span></dt><dd><p>

  139.        Specifies the client machine address(es) that this record

  140.        matches.  This field can contain either a host name, an IP

  141.        address range, or one of the special key words mentioned below.

  142.       </p><p>

  143.        An IP address range is specified using standard numeric notation

  144.        for the range's starting address, then a slash (<code class="literal">/</code>)

  145.        and a <acronym class="acronym">CIDR</acronym> mask length.  The mask

  146.        length indicates the number of high-order bits of the client

  147.        IP address that must match.  Bits to the right of this should

  148.        be zero in the given IP address.

  149.        There must not be any white space between the IP address, the

  150.        <code class="literal">/</code>, and the CIDR mask length.

  151.       </p><p>

  152.        Typical examples of an IPv4 address range specified this way are

  153.        <code class="literal">172.20.143.89/32</code> for a single host, or

  154.        <code class="literal">172.20.143.0/24</code> for a small network, or

  155.        <code class="literal">10.6.0.0/16</code> for a larger one.

  156.        An IPv6 address range might look like <code class="literal">::1/128</code>

  157.        for a single host (in this case the IPv6 loopback address) or

  158.        <code class="literal">fe80::7a31:c1ff:0000:0000/96</code> for a small

  159.        network.

  160.        <code class="literal">0.0.0.0/0</code> represents all

  161.        IPv4 addresses, and <code class="literal">::0/0</code> represents

  162.        all IPv6 addresses.

  163.        To specify a single host, use a mask length of 32 for IPv4 or

  164.        128 for IPv6.  In a network address, do not omit trailing zeroes.

  165.       </p><p>

  166.        An entry given in IPv4 format will match only IPv4 connections,

  167.        and an entry given in IPv6 format will match only IPv6 connections,

  168.        even if the represented address is in the IPv4-in-IPv6 range.

  169.        Note that entries in IPv6 format will be rejected if the system's

  170.        C library does not have support for IPv6 addresses.

  171.       </p><p>

  172.        You can also write <code class="literal">all</code> to match any IP address,

  173.        <code class="literal">samehost</code> to match any of the server's own IP

  174.        addresses, or <code class="literal">samenet</code> to match any address in any

  175.        subnet that the server is directly connected to.

  176.       </p><p>

  177.        If a host name is specified (anything that is not an IP address

  178.        range or a special key word is treated as a host name),

  179.        that name is compared with the result of a reverse name

  180.        resolution of the client's IP address (e.g., reverse DNS

  181.        lookup, if DNS is used).  Host name comparisons are case

  182.        insensitive.  If there is a match, then a forward name

  183.        resolution (e.g., forward DNS lookup) is performed on the host

  184.        name to check whether any of the addresses it resolves to are

  185.        equal to the client's IP address.  If both directions match,

  186.        then the entry is considered to match.  (The host name that is

  187.        used in <code class="filename">pg_hba.conf</code> should be the one that

  188.        address-to-name resolution of the client's IP address returns,

  189.        otherwise the line won't be matched.  Some host name databases

  190.        allow associating an IP address with multiple host names, but

  191.        the operating system will only return one host name when asked

  192.        to resolve an IP address.)

  193.       </p><p>

  194.        A host name specification that starts with a dot

  195.        (<code class="literal">.</code>) matches a suffix of the actual host

  196.        name.  So <code class="literal">.example.com</code> would match

  197.        <code class="literal">foo.example.com</code> (but not just

  198.        <code class="literal">example.com</code>).

  199.       </p><p>

  200.        When host names are specified

  201.        in <code class="filename">pg_hba.conf</code>, you should make sure that

  202.        name resolution is reasonably fast.  It can be of advantage to

  203.        set up a local name resolution cache such

  204.        as <code class="command">nscd</code>.  Also, you may wish to enable the

  205.        configuration parameter <code class="varname">log_hostname</code> to see

  206.        the client's host name instead of the IP address in the log.

  207.       </p><p>

  208.        These fields do not apply to <code class="literal">local</code> records.

  209.       </p><div class="note"><h3 class="title">Note</h3><p>

  210.         Users sometimes wonder why host names are handled

  211.         in this seemingly complicated way, with two name resolutions

  212.         including a reverse lookup of the client's IP address.  This

  213.         complicates use of the feature in case the client's reverse DNS

  214.         entry is not set up or yields some undesirable host name.

  215.         It is done primarily for efficiency: this way, a connection attempt

  216.         requires at most two resolver lookups, one reverse and one forward.

  217.         If there is a resolver problem with some address, it becomes only

  218.         that client's problem.  A hypothetical alternative

  219.         implementation that only did forward lookups would have to

  220.         resolve every host name mentioned in

  221.         <code class="filename">pg_hba.conf</code> during every connection attempt.

  222.         That could be quite slow if many names are listed.

  223.         And if there is a resolver problem with one of the host names,

  224.         it becomes everyone's problem.

  225.        </p><p>

  226.         Also, a reverse lookup is necessary to implement the suffix

  227.         matching feature, because the actual client host name needs to

  228.         be known in order to match it against the pattern.

  229.        </p><p>

  230.         Note that this behavior is consistent with other popular

  231.         implementations of host name-based access control, such as the

  232.         Apache HTTP Server and TCP Wrappers.

  233.        </p></div></dd><dt><span class="term"><em class="replaceable"><code>IP-address</code></em><br /></span><span class="term"><em class="replaceable"><code>IP-mask</code></em></span></dt><dd><p>

  234.        These two fields can be used as an alternative to the

  235.        <em class="replaceable"><code>IP-address</code></em><code class="literal">/</code><em class="replaceable"><code>mask-length</code></em>

  236.        notation.  Instead of

  237.        specifying the mask length, the actual mask is specified in a

  238.        separate column. For example, <code class="literal">255.0.0.0</code> represents an IPv4

  239.        CIDR mask length of 8, and <code class="literal">255.255.255.255</code> represents a

  240.        CIDR mask length of 32.

  241.       </p><p>

  242.        These fields do not apply to <code class="literal">local</code> records.

  243.       </p></dd><dt><span class="term"><em class="replaceable"><code>auth-method</code></em></span></dt><dd><p>

  244.        Specifies the authentication method to use when a connection matches

  245.        this record. The possible choices are summarized here; details

  246.        are in <a class="xref" href="auth-methods.html" title="20.3. Authentication Methods">Section 20.3</a>.

  247. 

  248.        </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="literal">trust</code></span></dt><dd><p>

  249.           Allow the connection unconditionally. This method

  250.           allows anyone that can connect to the

  251.           <span class="productname">PostgreSQL</span> database server to login as

  252.           any <span class="productname">PostgreSQL</span> user they wish,

  253.           without the need for a password or any other authentication.  See <a class="xref" href="auth-trust.html" title="20.4. Trust Authentication">Section 20.4</a> for details.

  254.          </p></dd><dt><span class="term"><code class="literal">reject</code></span></dt><dd><p>

  255.           Reject the connection unconditionally. This is useful for

  256.           <span class="quote">“<span class="quote">filtering out</span>”</span> certain hosts from a group, for example a

  257.           <code class="literal">reject</code> line could block a specific host from connecting,

  258.           while a later line allows the remaining hosts in a specific

  259.           network to connect.

  260.          </p></dd><dt><span class="term"><code class="literal">scram-sha-256</code></span></dt><dd><p>

  261.           Perform SCRAM-SHA-256 authentication to verify the user's

  262.           password. See <a class="xref" href="auth-password.html" title="20.5. Password Authentication">Section 20.5</a> for details.

  263.          </p></dd><dt><span class="term"><code class="literal">md5</code></span></dt><dd><p>

  264.           Perform SCRAM-SHA-256 or MD5 authentication to verify the

  265.           user's password. See <a class="xref" href="auth-password.html" title="20.5. Password Authentication">Section 20.5</a>

  266.           for details.

  267.          </p></dd><dt><span class="term"><code class="literal">password</code></span></dt><dd><p>

  268.           Require the client to supply an unencrypted password for

  269.           authentication.

  270.           Since the password is sent in clear text over the

  271.           network, this should not be used on untrusted networks.

  272.           See <a class="xref" href="auth-password.html" title="20.5. Password Authentication">Section 20.5</a> for details.

  273.          </p></dd><dt><span class="term"><code class="literal">gss</code></span></dt><dd><p>

  274.           Use GSSAPI to authenticate the user. This is only

  275.           available for TCP/IP connections. See <a class="xref" href="gssapi-auth.html" title="20.6. GSSAPI Authentication">Section 20.6</a> for details.  It can be used in conjunction

  276.           with GSSAPI encryption.

  277.          </p></dd><dt><span class="term"><code class="literal">sspi</code></span></dt><dd><p>

  278.           Use SSPI to authenticate the user. This is only

  279.           available on Windows. See <a class="xref" href="sspi-auth.html" title="20.7. SSPI Authentication">Section 20.7</a> for details.

  280.          </p></dd><dt><span class="term"><code class="literal">ident</code></span></dt><dd><p>

  281.           Obtain the operating system user name of the client

  282.           by contacting the ident server on the client

  283.           and check if it matches the requested database user name.

  284.           Ident authentication can only be used on TCP/IP

  285.           connections. When specified for local connections, peer

  286.           authentication will be used instead.

  287.           See <a class="xref" href="auth-ident.html" title="20.8. Ident Authentication">Section 20.8</a> for details.

  288.          </p></dd><dt><span class="term"><code class="literal">peer</code></span></dt><dd><p>

  289.           Obtain the client's operating system user name from the operating

  290.           system and check if it matches the requested database user name.

  291.           This is only available for local connections.

  292.           See <a class="xref" href="auth-peer.html" title="20.9. Peer Authentication">Section 20.9</a> for details.

  293.          </p></dd><dt><span class="term"><code class="literal">ldap</code></span></dt><dd><p>

  294.           Authenticate using an <acronym class="acronym">LDAP</acronym> server. See <a class="xref" href="auth-ldap.html" title="20.10. LDAP Authentication">Section 20.10</a> for details.

  295.          </p></dd><dt><span class="term"><code class="literal">radius</code></span></dt><dd><p>

  296.           Authenticate using a RADIUS server. See <a class="xref" href="auth-radius.html" title="20.11. RADIUS Authentication">Section 20.11</a> for details.

  297.          </p></dd><dt><span class="term"><code class="literal">cert</code></span></dt><dd><p>

  298.           Authenticate using SSL client certificates. See

  299.           <a class="xref" href="auth-cert.html" title="20.12. Certificate Authentication">Section 20.12</a> for details.

  300.          </p></dd><dt><span class="term"><code class="literal">pam</code></span></dt><dd><p>

  301.           Authenticate using the Pluggable Authentication Modules

  302.           (PAM) service provided by the operating system.  See <a class="xref" href="auth-pam.html" title="20.13. PAM Authentication">Section 20.13</a> for details.

  303.          </p></dd><dt><span class="term"><code class="literal">bsd</code></span></dt><dd><p>

  304.           Authenticate using the BSD Authentication service provided by the

  305.           operating system. See <a class="xref" href="auth-bsd.html" title="20.14. BSD Authentication">Section 20.14</a> for details.

  306.          </p></dd></dl></div><p>

  307. 

  308.       </p></dd><dt><span class="term"><em class="replaceable"><code>auth-options</code></em></span></dt><dd><p>

  309.        After the <em class="replaceable"><code>auth-method</code></em> field, there can be field(s) of

  310.        the form <em class="replaceable"><code>name</code></em><code class="literal">=</code><em class="replaceable"><code>value</code></em> that

  311.        specify options for the authentication method. Details about which

  312.        options are available for which authentication methods appear below.

  313.       </p><p>

  314.        In addition to the method-specific options listed below, there is one

  315.        method-independent authentication option <code class="literal">clientcert</code>, which

  316.        can be specified in any <code class="literal">hostssl</code> record.

  317.        This option can be set to <code class="literal">verify-ca</code> or

  318.        <code class="literal">verify-full</code>. Both options require the client

  319.        to present a valid (trusted) SSL certificate, while

  320.        <code class="literal">verify-full</code> additionally enforces that the

  321.        <code class="literal">cn</code> (Common Name) in the certificate matches

  322.        the username or an applicable mapping.

  323.        This behavior is similar to the <code class="literal">cert</code> authentication

  324.        method (see <a class="xref" href="auth-cert.html" title="20.12. Certificate Authentication">Section 20.12</a>) but enables pairing

  325.        the verification of client certificates with any authentication

  326.        method that supports <code class="literal">hostssl</code> entries.

  327.       </p></dd></dl></div><p>

  328.   </p><p>

  329.    Files included by <code class="literal">@</code> constructs are read as lists of names,

  330.    which can be separated by either whitespace or commas.  Comments are

  331.    introduced by <code class="literal">#</code>, just as in

  332.    <code class="filename">pg_hba.conf</code>, and nested <code class="literal">@</code> constructs are

  333.    allowed.  Unless the file name following <code class="literal">@</code> is an absolute

  334.    path, it is taken to be relative to the directory containing the

  335.    referencing file.

  336.   </p><p>

  337.    Since the <code class="filename">pg_hba.conf</code> records are examined

  338.    sequentially for each connection attempt, the order of the records is

  339.    significant. Typically, earlier records will have tight connection

  340.    match parameters and weaker authentication methods, while later

  341.    records will have looser match parameters and stronger authentication

  342.    methods. For example, one might wish to use <code class="literal">trust</code>

  343.    authentication for local TCP/IP connections but require a password for

  344.    remote TCP/IP connections. In this case a record specifying

  345.    <code class="literal">trust</code> authentication for connections from 127.0.0.1 would

  346.    appear before a record specifying password authentication for a wider

  347.    range of allowed client IP addresses.

  348.   </p><p>

  349.    The <code class="filename">pg_hba.conf</code> file is read on start-up and when

  350.    the main server process receives a

  351.    <span class="systemitem">SIGHUP</span><a id="id-1.6.7.8.9.3" class="indexterm"></a>

  352.    signal. If you edit the file on an

  353.    active system, you will need to signal the postmaster

  354.    (using <code class="literal">pg_ctl reload</code>, calling the SQL function

  355.    <code class="function">pg_reload_conf()</code>, or using <code class="literal">kill

  356.    -HUP</code>) to make it re-read the file.

  357.   </p><div class="note"><h3 class="title">Note</h3><p>

  358.     The preceding statement is not true on Microsoft Windows: there, any

  359.     changes in the <code class="filename">pg_hba.conf</code> file are immediately

  360.     applied by subsequent new connections.

  361.    </p></div><p>

  362.    The system view

  363.    <a class="link" href="view-pg-hba-file-rules.html" title="51.72. pg_hba_file_rules"><code class="structname">pg_hba_file_rules</code></a>

  364.    can be helpful for pre-testing changes to the <code class="filename">pg_hba.conf</code>

  365.    file, or for diagnosing problems if loading of the file did not have the

  366.    desired effects.  Rows in the view with

  367.    non-null <code class="structfield">error</code> fields indicate problems in the

  368.    corresponding lines of the file.

  369.   </p><div class="tip"><h3 class="title">Tip</h3><p>

  370.     To connect to a particular database, a user must not only pass the

  371.     <code class="filename">pg_hba.conf</code> checks, but must have the

  372.     <code class="literal">CONNECT</code> privilege for the database.  If you wish to

  373.     restrict which users can connect to which databases, it's usually

  374.     easier to control this by granting/revoking <code class="literal">CONNECT</code> privilege

  375.     than to put the rules in <code class="filename">pg_hba.conf</code> entries.

  376.    </p></div><p>

  377.    Some examples of <code class="filename">pg_hba.conf</code> entries are shown in

  378.    <a class="xref" href="auth-pg-hba-conf.html#EXAMPLE-PG-HBA.CONF" title="Example 20.1. Example pg_hba.conf Entries">Example 20.1</a>. See the next section for details on the

  379.    different authentication methods.

  380.   </p><div class="example" id="EXAMPLE-PG-HBA.CONF"><p class="title"><strong>Example 20.1. Example <code class="filename">pg_hba.conf</code> Entries</strong></p><div class="example-contents"><pre class="programlisting">

  381. # Allow any user on the local system to connect to any database with

  382. # any database user name using Unix-domain sockets (the default for local

  383. # connections).

  384. #

  385. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  386. local   all             all                                     trust

  387. 

  388. # The same using local loopback TCP/IP connections.

  389. #

  390. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  391. host    all             all             127.0.0.1/32            trust

  392. 

  393. # The same as the previous line, but using a separate netmask column

  394. #

  395. # TYPE  DATABASE        USER            IP-ADDRESS      IP-MASK             METHOD

  396. host    all             all             127.0.0.1       255.255.255.255     trust

  397. 

  398. # The same over IPv6.

  399. #

  400. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  401. host    all             all             ::1/128                 trust

  402. 

  403. # The same using a host name (would typically cover both IPv4 and IPv6).

  404. #

  405. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  406. host    all             all             localhost               trust

  407. 

  408. # Allow any user from any host with IP address 192.168.93.x to connect

  409. # to database "postgres" as the same user name that ident reports for

  410. # the connection (typically the operating system user name).

  411. #

  412. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  413. host    postgres        all             192.168.93.0/24         ident

  414. 

  415. # Allow any user from host 192.168.12.10 to connect to database

  416. # "postgres" if the user's password is correctly supplied.

  417. #

  418. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  419. host    postgres        all             192.168.12.10/32        scram-sha-256

  420. 

  421. # Allow any user from hosts in the example.com domain to connect to

  422. # any database if the user's password is correctly supplied.

  423. #

  424. # Require SCRAM authentication for most users, but make an exception

  425. # for user 'mike', who uses an older client that doesn't support SCRAM

  426. # authentication.

  427. #

  428. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  429. host    all             mike            .example.com            md5

  430. host    all             all             .example.com            scram-sha-256

  431. 

  432. # In the absence of preceding "host" lines, these three lines will

  433. # reject all connections from 192.168.54.1 (since that entry will be

  434. # matched first), but allow GSSAPI-encrypted connections from anywhere else

  435. # on the Internet.  The zero mask causes no bits of the host IP address to

  436. # be considered, so it matches any host.  Unencrypted GSSAPI connections

  437. # (which "fall through" to the third line since "hostgssenc" only matches

  438. # encrypted GSSAPI connections) are allowed, but only from 192.168.12.10.

  439. #

  440. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  441. host    all             all             192.168.54.1/32         reject

  442. hostgssenc all          all             0.0.0.0/0               gss

  443. host    all             all             192.168.12.10/32        gss

  444. 

  445. # Allow users from 192.168.x.x hosts to connect to any database, if

  446. # they pass the ident check.  If, for example, ident says the user is

  447. # "bryanh" and he requests to connect as PostgreSQL user "guest1", the

  448. # connection is allowed if there is an entry in pg_ident.conf for map

  449. # "omicron" that says "bryanh" is allowed to connect as "guest1".

  450. #

  451. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  452. host    all             all             192.168.0.0/16          ident map=omicron

  453. 

  454. # If these are the only three lines for local connections, they will

  455. # allow local users to connect only to their own databases (databases

  456. # with the same name as their database user name) except for administrators

  457. # and members of role "support", who can connect to all databases.  The file

  458. # $PGDATA/admins contains a list of names of administrators.  Passwords

  459. # are required in all cases.

  460. #

  461. # TYPE  DATABASE        USER            ADDRESS                 METHOD

  462. local   sameuser        all                                     md5

  463. local   all             @admins                                 md5

  464. local   all             +support                                md5

  465. 

  466. # The last two lines above can be combined into a single line:

  467. local   all             @admins,+support                        md5

  468. 

  469. # The database column can also use lists and file names:

  470. local   db1,db2,@demodbs  all                                   md5

  471. </pre></div></div><br class="example-break" /></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="client-authentication.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="client-authentication.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="auth-username-maps.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 20. Client Authentication </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 20.2. User Name Maps</td></tr></table></div></body></html>
上海开阖软件有限公司 沪ICP备12045867号-1