2022年02月13日 21:10
# PostgreSQL Client Authentication Configuration File
# ===================================================
# Refer to the "Client Authentication" section in the PostgreSQL
# documentation for a complete description of this file. A short
# synopsis follows.
This file controls: which hosts are allowed to connect, how clients
are authenticated, which PostgreSQL user names they can use, which
databases they can access. Records take one of these forms:
# local DATABASE USER METHOD [OPTIONS]
# host DATABASE USER ADDRESS METHOD [OPTIONS]
# hostssl DATABASE USER ADDRESS METHOD [OPTIONS]
# hostnossl DATABASE USER ADDRESS METHOD [OPTIONS]
# hostgssenc DATABASE USER ADDRESS METHOD [OPTIONS]
# hostnogssenc DATABASE USER ADDRESS METHOD [OPTIONS]
# (The uppercase items must be replaced by actual values.)
# The first field is the connection type: "local" is a Unix-domain
# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
# non-SSL TCP/IP socket. Similarly, "hostgssenc" uses a
# GSSAPI-encrypted TCP/IP socket, while "hostnogssenc" uses a
# non-GSSAPI socket.
# DATABASE can be "all", "sameuser", "samerole", "replication", a
# database name, or a comma-separated list thereof. The "all"
# keyword does not match "replication". Access to replication
# must be enabled in a separate record (see example below).
# USER can be "all", a user name, a group name prefixed with "+", or a
# comma-separated list thereof. In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names
# from a separate file.
# ADDRESS specifies the set of hosts the record matches. It can be a
# host name, or it is made up of an IP address and a CIDR mask that is
# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
# specifies the number of significant bits in the mask. A host name
# that starts with a dot (.) matches a suffix of the actual host name.
# Alternatively, you can write an IP address and netmask in separate
# columns to specify the set of hosts. Instead of a CIDR-address, you
# can write "samehost" to match any of the server's own IP addresses,
# or "samenet" to match any address in any subnet that the server is
# directly connected to.
# METHOD can be "trust", "reject", "md5", "password", "scram-sha-256",
# "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert".
# Note that "password" sends passwords in clear text; "md5" or
# "scram-sha-256" are preferred since they send encrypted passwords.
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE. The available options depend on the different
# authentication methods -- refer to the "Client Authentication"
# section in the documentation for a list of which options are
# available for which authentication methods.
# Database and user names containing spaces, commas, quotes and other
# special characters must be quoted. Quoting one of the keywords
# "all", "sameuser", "samerole" or "replication" makes the name lose
# its special character, and just match a database or username with
# that name.
# This file is read on server startup and when the server receives a
# SIGHUP signal. If you edit the file on a running system, you have to
# SIGHUP the server for the changes to take effect, run "pg_ctl reload",
# or execute "SELECT pg_reload_conf()".
# Put your actual configuration here
# ----------------------------------
# If you want to allow non-local connections, you need to add more
# "host" records. In that case you will also need to make PostgreSQL
# listen on a non-local interface via the listen_addresses
# configuration parameter, or via the -i or -h command line switches.
# CAUTION: Configuring the system for local "trust" authentication
# allows any local user to connect as any PostgreSQL user, including
# the database superuser. If you do not trust all your local users,
# use another authentication method.
# TYPE DATABASE USER ADDRESS METHOD
# "local" is for Unix domain socket connections only
# "local" は Unix ドメインソケット接続のみ
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
# レプリケーション特権のユーザにより, ローカルホストから
# レプリケーション接続できるようにする.
local replication all trust
host replication all 127.0.0.1/32 trust
host replication all ::1/128 trust
# ローカルシステム上で
# 全てのユーザが任意の DB に任意の DB ユーザ名で
# Unix ドメインソケットを介して接続することを許可する
# (ローカル接続のデフォルト)
#
# TYPE DATABASE USER ADDRESS METHOD
local all all trust
# 上記と同じことを
# ローカルループバックの
# TCP/IP 接続で行う
#
# TYPE DATABASE USER ADDRESS METHOD
host all all 127.0.0.1/32 trust
# 上記と同じ
# 独立したネットマスク列を使用
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host all all 127.0.0.1 255.255.255.255 trust
# 上記と同じ
# IPv6 を使用
#
# TYPE DATABASE USER ADDRESS METHOD
host all all ::1/128 trust
# 上記と同じ
# ホスト名を使う (通常は IPv4, IPv6 の両方をカバー)
#
# TYPE DATABASE USER ADDRESS METHOD
host all all localhost trust
# (Identification プロトコルに基づく) ident に基づいて
# IP アドレス 192.168.93.x のホストのユーザ (典型的には OS のユーザ名) が
# DB 名 postgres へ接続することを許可する
#
# TYPE DATABASE USER ADDRESS METHOD
host postgres all 192.168.93.0/24 ident
# SCRAM-SHA-256 認証に基づいて
# ホスト 192.168.12.10 からのユーザによって
# パスワードが正しく入力された場合に
# DB 名 postgres へ接続することを許可する
#
# TYPE DATABASE USER ADDRESS METHOD
host postgres all 192.168.12.10/32 scram-sha-256
# exmaple.com ドメイン内のホストからのユーザによって
# パスワードが正しく入力された場合に
# すべての DB へ接続することを許可する
#
# SCRAM 認証をサポートしない古いクライアントを使うユーザ 'mike' には
# 別のメソッドを用意
#
# TYPE DATABASE USER ADDRESS METHOD
host all mike .example.com md5
host all all .example.com scram-sha-256
# --- これ以外に host 行がない場合 ---
# 192.168.54.1 からの接続をすべて拒否 (reject) するが
# 暗号化された GSSAPI 接続はインターネット上のどこからでも許可する
# (ゼロマスクは IP アドレスのビットを考慮しない)
# GSSAPI 接続でも非暗号化のものは 192.168.12.10 からのみ許可
#
# TYPE DATABASE USER ADDRESS METHOD
host all all 192.168.54.1/32 reject
hostgssenc all all 0.0.0.0/0 gss
host all all 192.168.12.10/32 gss
# ホスト 192.168.x.x からのユーザが
# ファイル data/pg_ident.conf での
# マップ名 omicron のユーザマッピングに対応した ident 検査をパスすれば
# すべての DB へのアクセスを許可する
# https://www.postgresql.jp/document/13/html/auth-username-maps.html#EXAMPLE-PG-IDENT.CONF
# の 例20.2 を参照
#
# TYPE DATABASE USER ADDRESS METHOD
host all all 192.168.0.0/16 ident map=omicron
# --- この 3 行以外の他に構成行がない場合 ---
# ローカルユーザはその DB ユーザ名と同じ名前の DB にのみ接続可 (sameusr)
# ファイル $PGDATA/adimns にリストされているユーザと
# ロール support のユーザはすべての DB に接続可
# 要パスワード
#
# TYPE DATABASE USER ADDRESS METHOD
local sameuser all md5
local all @admins md5
local all +support md5
# 上記最後の 2 行はカンマ区切りのリストとして 1 行にまとめられる
local all @admins,+support md5
# DB 列でもカンマ区切りで DB 名やファイル名をリスト可能
local db1,db2,@demodbs all md5