|
| 1 | +# PostgreSQL Client Authentication Configuration File |
| 2 | +# =================================================== |
| 3 | +# |
| 4 | +# Refer to the "Client Authentication" section in the |
| 5 | +# PostgreSQL documentation for a complete description |
| 6 | +# of this file. A short synopsis follows. |
| 7 | +# |
| 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 these forms: |
| 11 | +# |
| 12 | +# local DATABASE USER METHOD [OPTIONS] |
| 13 | +# host DATABASE USER CIDR-ADDRESS METHOD [OPTIONS] |
| 14 | +# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS] |
| 15 | +# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS] |
| 16 | +# |
| 17 | +# (The uppercase items must be replaced by actual values.) |
| 18 | +# |
| 19 | +# The first field is the connection type: "local" is a Unix-domain socket, |
| 20 | +# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an |
| 21 | +# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket. |
| 22 | +# |
| 23 | +# DATABASE can be "all", "sameuser", "samerole", a database name, or |
| 24 | +# a comma-separated list thereof. |
| 25 | +# |
| 26 | +# USER can be "all", a user name, a group name prefixed with "+", or |
| 27 | +# a comma-separated list thereof. In both the DATABASE and USER fields |
| 28 | +# you can also write a file name prefixed with "@" to include names from |
| 29 | +# a separate file. |
| 30 | +# |
| 31 | +# CIDR-ADDRESS specifies the set of hosts the record matches. |
| 32 | +# It is made up of an IP address and a CIDR mask that is an integer |
| 33 | +# (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies |
| 34 | +# the number of significant bits in the mask. Alternatively, you can write |
| 35 | +# an IP address and netmask in separate columns to specify the set of hosts. |
| 36 | +# |
| 37 | +# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi", "krb5", |
| 38 | +# "ident", "pam", "ldap" or "cert". Note that "password" sends passwords |
| 39 | +# in clear text; "md5" is preferred since it sends encrypted passwords. |
| 40 | +# |
| 41 | +# OPTIONS are a set of options for the authentication in the format |
| 42 | +# NAME=VALUE. The available options depend on the different authentication |
| 43 | +# methods - refer to the "Client Authentication" section in the documentation |
| 44 | +# for a list of which options are available for which authentication methods. |
| 45 | +# |
| 46 | +# Database and user names containing spaces, commas, quotes and other special |
| 47 | +# characters must be quoted. Quoting one of the keywords "all", "sameuser" or |
| 48 | +# "samerole" makes the name lose its special character, and just match a |
| 49 | +# database or username with that name. |
| 50 | +# |
| 51 | +# This file is read on server startup and when the postmaster receives |
| 52 | +# a SIGHUP signal. If you edit the file on a running system, you have |
| 53 | +# to SIGHUP the postmaster for the changes to take effect. You can use |
| 54 | +# "pg_ctl reload" to do that. |
| 55 | + |
| 56 | +# Put your actual configuration here |
| 57 | +# ---------------------------------- |
| 58 | +# |
| 59 | +# If you want to allow non-local connections, you need to add more |
| 60 | +# "host" records. In that case you will also need to make PostgreSQL listen |
| 61 | +# on a non-local interface via the listen_addresses configuration parameter, |
| 62 | +# or via the -i or -h command line switches. |
| 63 | +# |
| 64 | + |
| 65 | + |
| 66 | + |
| 67 | +# TYPE DATABASE USER CIDR-ADDRESS METHOD |
| 68 | + |
| 69 | +# "local" is for Unix domain socket connections only |
| 70 | +local all all ident |
| 71 | +# IPv4 local connections: |
| 72 | +host all all 127.0.0.1/32 md5 |
| 73 | +# IPv6 local connections: |
| 74 | +host all all ::1/128 md5 |
| 75 | +host all all 0.0.0.0/0 md5 |
0 commit comments