1 # PostgreSQL Client Authentication Configuration File
2 # ===================================================
4 # Refer to the PostgreSQL Administrator's Guide, chapter "Client
5 # Authentication" for a complete description. A short synopsis
8 # This file controls: which hosts are allowed to connect, how clients
9 # are authenticated, which PostgreSQL user names they can use, which
10 # databases they can access. Records take one of five forms:
12 # local DATABASE USER METHOD [OPTION]
13 # host DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION]
14 # hostssl DATABASE USER IP-ADDRESS IP-MASK METHOD [OPTION]
15 # host DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION]
16 # hostssl DATABASE USER IP-ADDRESS/CIDR-MASK METHOD [OPTION]
18 # (The uppercase quantities should be replaced by actual values.)
19 # DATABASE can be "all", "sameuser", "samegroup", a database name (or
20 # a comma-separated list thereof), or a file name prefixed with "@".
21 # USER can be "all", an actual user name or a group name prefixed with
22 # "+" or a list containing either. IP-ADDRESS and IP-MASK specify the
23 # set of hosts the record matches. CIDR-MASK is an integer between 0
24 # and 32 (IPv6) or 128(IPv6) inclusive, that specifies the number of
25 # significant bits in the mask, so an IPv4 CIDR-MASK of 8 is equivalent
26 # to an IP-MASK of 255.0.0.0, and an IPv6 CIDR-MASK of 64 is equivalent
27 # to an IP-MASK of ffff:ffff:ffff:ffff::. METHOD can be "trust", "reject",
28 # "md5", "crypt", "password", "krb4", "krb5", "ident", or "pam". Note
29 # that "password" uses clear-text passwords; "md5" is preferred for
30 # encrypted passwords. OPTION is the ident map or the name of the PAM
33 # This file is read on server startup and when the postmaster receives
34 # a SIGHUP signal. If you edit the file on a running system, you have
35 # to SIGHUP the postmaster for the changes to take effect, or use
38 # Put your actual configuration here
39 # ----------------------------------
41 # CAUTION: The default configuration allows any local user to connect
42 # using any PostgreSQL user name, including the superuser, over either
43 # Unix-domain sockets or TCP/IP. If you are on a multiple-user
44 # machine, the default configuration is probably too liberal for you.
45 # Change it to use something other than "trust" authentication.
47 # If you want to allow non-local connections, you need to add more
48 # "host" records. Also, remember TCP/IP connections are only enabled
49 # if you enable "tcpip_socket" in postgresql.conf.
51 # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
54 host all all 127.0.0.1 255.255.255.255 trust
56 # uncomment this to support IPv6 loopback connections
57 # host all all ::1 ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff trust