<HTML
><HEAD
><TITLE
>Client Authentication</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.73
"><LINK
REV="MADE"
HREF="mailto:pgsql-docs@postgresql.org"><LINK
REL="HOME"
TITLE="PostgreSQL 7.3.2 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="PostgreSQL 7.3.2 Administrator's Guide"
HREF="admin.html"><LINK
REL="PREVIOUS"
TITLE="Destroying a Database"
HREF="manage-ag-dropdb.html"><LINK
REL="NEXT"
TITLE="Authentication methods"
HREF="auth-methods.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
NAME="creation"
CONTENT="2003-02-03T20:17:34"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PostgreSQL 7.3.2 Documentation</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="manage-ag-dropdb.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="auth-methods.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="CLIENT-AUTHENTICATION"
>Chapter 6. Client Authentication</A
></H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>6.1. <A
HREF="client-authentication.html#AUTH-PG-HBA-CONF"
>The <TT
CLASS="FILENAME"
>pg_hba.conf</TT
> file</A
></DT
><DT
>6.2. <A
HREF="auth-methods.html"
>Authentication methods</A
></DT
><DD
><DL
><DT
>6.2.1. <A
HREF="auth-methods.html#AUTH-TRUST"
>Trust authentication</A
></DT
><DT
>6.2.2. <A
HREF="auth-methods.html#AUTH-PASSWORD"
>Password authentication</A
></DT
><DT
>6.2.3. <A
HREF="auth-methods.html#KERBEROS-AUTH"
>Kerberos authentication</A
></DT
><DT
>6.2.4. <A
HREF="auth-methods.html#AUTH-IDENT"
>Ident-based authentication</A
></DT
><DT
>6.2.5. <A
HREF="auth-methods.html#AUTH-PAM"
>PAM Authentication</A
></DT
></DL
></DD
><DT
>6.3. <A
HREF="client-authentication-problems.html"
>Authentication problems</A
></DT
></DL
></DIV
><A
NAME="AEN21217"
></A
><P
> When a client application connects to the database server, it
specifies which <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> user name it
wants to connect as, much the same way one logs into a Unix computer
as a particular user. Within the SQL environment the active database
user name determines access privileges to database objects -- see
<A
HREF="user-manag.html"
>Chapter 4</A
> for more information. Therefore, it is
essential to restrict which database users can connect.
</P
><P
> <I
CLASS="FIRSTTERM"
>Authentication</I
> is the process by which the
database server establishes the identity of the client, and by
extension determines whether the client application (or the user
who runs the client application) is permitted to connect with the
user name that was requested.
</P
><P
> <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> offers a number of different
client authentication methods. The method used to authenticate a
particular client connection can be selected on the basis of
(client) host address, database, and user.
</P
><P
> <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> user names are logically
separate from user names of the operating system in which the server
runs. If all the users of a particular server also have accounts on
the server's machine, it makes sense to assign database user names
that match their operating system user names. However, a server that
accepts remote connections may have many users who have no local
account, and in such cases there need be no connection between
database user names and OS user names.
</P
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AUTH-PG-HBA-CONF"
>6.1. The <TT
CLASS="FILENAME"
>pg_hba.conf</TT
> file</A
></H1
><A
NAME="AEN21231"
></A
><P
> Client authentication is controlled by the file
<TT
CLASS="FILENAME"
>pg_hba.conf</TT
> in the data directory, e.g.,
<TT
CLASS="FILENAME"
>/usr/local/pgsql/data/pg_hba.conf</TT
>.
(<SPAN
CLASS="ACRONYM"
>HBA</SPAN
> stands for host-based authentication.) A default
<TT
CLASS="FILENAME"
>pg_hba.conf</TT
> file is installed when the data
directory is initialized by <TT
CLASS="COMMAND"
>initdb</TT
>.
</P
><P
> The general format of the <TT
CLASS="FILENAME"
>pg_hba.conf</TT
> file is
a set of records, one per line. Blank lines are ignored, as is any
text after the <SPAN
CLASS="QUOTE"
>"#"</SPAN
> comment character. A record is made
up of a number of fields which are separated by spaces and/or tabs.
Fields can contain white space if the field value is quoted. Records
cannot be continued across lines.
</P
><P
> Each record specifies a connection type, a client IP address range
(if relevant for the connection type), a database name, a user name,
and the authentication method to be used for connections matching
these parameters. The first record with a matching connection type,
client address, requested database, and user name is used to perform
authentication. There is no <SPAN
CLASS="QUOTE"
>"fall-through"</SPAN
> or
<SPAN
CLASS="QUOTE"
>"backup"</SPAN
>: if one record is chosen and the authentication
fails, subsequent records are not considered. If no record matches,
access is denied.
</P
><P
> A record may have one of the three formats
</P><PRE
CLASS="SYNOPSIS"
>local <TT
CLASS="REPLACEABLE"
><I
>database</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>user</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>authentication-method</I
></TT
> [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="REPLACEABLE"
><I
>authentication-option</I
></TT
></SPAN
>]
host <TT
CLASS="REPLACEABLE"
><I
>database</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>user</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>IP-address</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>IP-mask</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>authentication-method</I
></TT
> [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="REPLACEABLE"
><I
>authentication-option</I
></TT
></SPAN
>]
hostssl <TT
CLASS="REPLACEABLE"
><I
>database</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>user</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>IP-address</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>IP-mask</I
></TT
> <TT
CLASS="REPLACEABLE"
><I
>authentication-method</I
></TT
> [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="REPLACEABLE"
><I
>authentication-option</I
></TT
></SPAN
>]
</PRE
><P>
The meaning of the fields is as follows:
<P
></P
></P><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="LITERAL"
>local</TT
></DT
><DD
><P
> This record matches connection attempts using Unix domain
sockets. Without a record of this type, Unix-domain socket
connections are disallowed
</P
></DD
><DT
><TT
CLASS="LITERAL"
>host</TT
></DT
><DD
><P
> This record matches connection attempts using TCP/IP networks.
Note that TCP/IP connections are disabled unless the server is
started with the <TT
CLASS="OPTION"
>-i</TT
> option or the
<TT
CLASS="LITERAL"
>tcpip_socket</TT
> <TT
CLASS="FILENAME"
>postgresql.conf</TT
>
configuration parameter is enabled.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>hostssl</TT
></DT
><DD
><P
> This record matches connection attempts using SSL over TCP/IP.
<TT
CLASS="LITERAL"
>host</TT
> records will match either SSL or
non-SSL connection attempts, but <TT
CLASS="LITERAL"
>hostssl</TT
>
records require SSL connections.
</P
><P
> To be able make use of this option the server must be built
with SSL support enabled. Furthermore, SSL must be enabled by
enabling the option <TT
CLASS="LITERAL"
>ssl</TT
> in
<TT
CLASS="FILENAME"
>postgresql.conf</TT
> (see <A
HREF="runtime-config.html"
>Section 3.4</A
>).
</P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>database</I
></TT
></DT
><DD
><P
> Specifies which databases this record matches. The value
<TT
CLASS="LITERAL"
>all</TT
> specifies that it matches all databases.
The value <TT
CLASS="LITERAL"
>sameuser</TT
> specifies that the record
matches if the requested database has the same name as the
requested user. The value <TT
CLASS="LITERAL"
>samegroup</TT
> specifies that
the requested user must a member of the group with the same
name as the requested database. Otherwise, this is the name of
a specific <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> database.
Multiple database names can be supplied by separating them with
commas. A file containing database names can be specified by
preceding the file name with <TT
CLASS="LITERAL"
>@</TT
>. The file must be in
the same directory as <TT
CLASS="FILENAME"
>pg_hba.conf</TT
>.
</P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>user</I
></TT
></DT
><DD
><P
> Specifies which PostgreSQL users this record matches. The value
<TT
CLASS="LITERAL"
>all</TT
> specifies that it matches all users.
Otherwise, this is the name of a specific
<SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> user. Multiple user names
can be supplied by separating them with commas. Group names can
be specified by preceding the group name with <TT
CLASS="LITERAL"
>+</TT
>. A
file containing user names can be specified by preceding the
file name with <TT
CLASS="LITERAL"
>@</TT
>. The file must be in the same
directory as <TT
CLASS="FILENAME"
>pg_hba.conf</TT
>.
</P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>IP-address</I
></TT
><BR><TT
CLASS="REPLACEABLE"
><I
>IP-mask</I
></TT
></DT
><DD
><P
> These two fields contain IP address/mask values in standard
dotted decimal notation. (IP addresses can only be specified
numerically, not as domain or host names.) Taken together they
specify the client machine IP addresses that this record
matches. The precise logic is that
<A
NAME="AEN21319"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><DIV
CLASS="INFORMALFIGURE"
><A
NAME="AEN21320"
></A
><P
></P
><PRE
CLASS="PROGRAMLISTING"
>(<TT
CLASS="REPLACEABLE"
><I
>actual-IP-address</I
></TT
> xor <TT
CLASS="REPLACEABLE"
><I
>IP-address-field</I
></TT
>) and <TT
CLASS="REPLACEABLE"
><I
>IP-mask-field</I
></TT
></PRE
><P
></P
></DIV
></BLOCKQUOTE
>
must be zero for the record to match. (Of course IP addresses
can be spoofed but this consideration is beyond the scope of
<SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
>.)
</P
><P
> These fields only apply to <TT
CLASS="LITERAL"
>host</TT
> and
<TT
CLASS="LITERAL"
>hostssl</TT
> records.
</P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>authentication-method</I
></TT
></DT
><DD
><P
> Specifies the authentication method to use when connecting via
this record. The possible choices are summarized here; details
are in <A
HREF="auth-methods.html"
>Section 6.2</A
>.
<P
></P
></P><DIV
CLASS="VARIABLELIST"
><DL
><DT
><TT
CLASS="LITERAL"
>trust</TT
></DT
><DD
><P
> The connection is allowed unconditionally. This method
allows anyone that can connect to the
<SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> database to login as
any <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> user they like,
without the need for a password. See <A
HREF="auth-methods.html#AUTH-TRUST"
>Section 6.2.1</A
> for details.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>reject</TT
></DT
><DD
><P
> The connection is rejected unconditionally. This is useful for
<SPAN
CLASS="QUOTE"
>"filtering out"</SPAN
> certain hosts from a group.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>md5</TT
></DT
><DD
><P
> Requires the client to supply an MD5 encrypted password for
authentication. This is the only method that allows encrypted
passwords to be stored in <TT
CLASS="STRUCTNAME"
>pg_shadow</TT
>.
See <A
HREF="auth-methods.html#AUTH-PASSWORD"
>Section 6.2.2</A
> for details.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>crypt</TT
></DT
><DD
><P
> Like <TT
CLASS="LITERAL"
>md5</TT
> method but uses older crypt
encryption, which is needed for pre-7.2 clients.
<TT
CLASS="LITERAL"
>md5</TT
> is preferred for 7.2 and later clients.
See <A
HREF="auth-methods.html#AUTH-PASSWORD"
>Section 6.2.2</A
> for details.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>password</TT
></DT
><DD
><P
> Same as "md5", but the password is sent in clear text over the
network. This should not be used on untrusted networks.
See <A
HREF="auth-methods.html#AUTH-PASSWORD"
>Section 6.2.2</A
> for details.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>krb4</TT
></DT
><DD
><P
> Kerberos V4 is used to authenticate the user. This is only
available for TCP/IP connections. See <A
HREF="auth-methods.html#KERBEROS-AUTH"
>Section 6.2.3</A
> for details.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>krb5</TT
></DT
><DD
><P
> Kerberos V5 is used to authenticate the user. This is only
available for TCP/IP connections. See <A
HREF="auth-methods.html#KERBEROS-AUTH"
>Section 6.2.3</A
> for details.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>ident</TT
></DT
><DD
><P
> Obtain the operating system user name of the client (for
TCP/IP connections by contacting the ident server on the
client, for local connections by getting it from the
operating system) and check if the user is allowed to
connect as the requested database user by consulting the map
specified after the <TT
CLASS="LITERAL"
>ident</TT
> key word.
</P
><P
> If you use the map <TT
CLASS="LITERAL"
>sameuser</TT
>, the user
names are assumed to be identical. If not, the map name is
looked up in the file <TT
CLASS="FILENAME"
>pg_ident.conf</TT
>
in the same directory as <TT
CLASS="FILENAME"
>pg_hba.conf</TT
>.
The connection is accepted if that file contains an
entry for this map name with the ident-supplied user name
and the requested <SPAN
CLASS="PRODUCTNAME"
>PostgreSQL</SPAN
> user
name.
</P
><P
> For local connections, this only works on machines that
support Unix-domain socket credentials (currently
<SPAN
CLASS="SYSTEMITEM"
>Linux</SPAN
>, <SPAN
CLASS="SYSTEMITEM"
>FreeBSD</SPAN
>, <SPAN
CLASS="SYSTEMITEM"
>NetBSD</SPAN
>,
and <SPAN
CLASS="SYSTEMITEM"
>BSD/OS</SPAN
>).
</P
><P
> See <A
HREF="auth-methods.html#AUTH-IDENT"
>Section 6.2.4</A
> below for details.
</P
></DD
><DT
><TT
CLASS="LITERAL"
>pam</TT
></DT
><DD
><P
> Authenticate using the Pluggable Authentication Modules
(PAM) service provided by the operating system. See <A
HREF="auth-methods.html#AUTH-PAM"
>Section 6.2.5</A
> for details.
</P
></DD
></DL
></DIV
><P>
</P
></DD
><DT
><TT
CLASS="REPLACEABLE"
><I
>authentication-option</I
></TT
></DT
><DD
><P
> The meaning of this optional field depends on the chosen
authentication method and is described in the next section.
</P
></DD
></DL
></DIV
><P>
</P
><P
> Since the <TT
CLASS="FILENAME"
>pg_hba.conf</TT
> records are examined
sequentially for each connection attempt, the order of the records is
significant. Typically, earlier records will have tight connection
match parameters and weaker authentication methods, while later
records will have looser match parameters and stronger authentication
methods. For example, one might wish to use <TT
CLASS="LITERAL"
>trust</TT
>
authentication for local TCP connections but require a password for
remote TCP connections. In this case a record specifying
<TT
CLASS="LITERAL"
>trust</TT
> authentication for connections from 127.0.0.1 would
appear before a record specifying password authentication for a wider
range of allowed client IP addresses.
</P
><DIV
CLASS="IMPORTANT"
><BLOCKQUOTE
CLASS="IMPORTANT"
><P
><B
>Important: </B
> Do not prevent the superuser from accessing the template1
database. Various utility commands need access to template1.
</P
></BLOCKQUOTE
></DIV
><P
> <A
NAME="AEN21419"
></A
>
The <TT
CLASS="FILENAME"
>pg_hba.conf</TT
> file is read on start-up and when
the <SPAN
CLASS="APPLICATION"
>postmaster</SPAN
> receives a
<SPAN
CLASS="SYSTEMITEM"
>SIGHUP</SPAN
> signal. If you edit the file on an
active system, you will need to signal the <SPAN
CLASS="APPLICATION"
>postmaster</SPAN
>
(using <TT
CLASS="LITERAL"
>pg_ctl reload</TT
> or <TT
CLASS="LITERAL"
>kill -HUP</TT
>) to make it
re-read the file.
</P
><P
> An example of a <TT
CLASS="FILENAME"
>pg_hba.conf</TT
> file is shown in
<A
HREF="client-authentication.html#EXAMPLE-PG-HBA.CONF"
>Example 6-1</A
>. See below for details on the
different authentication methods.
<DIV
CLASS="EXAMPLE"
><A
NAME="EXAMPLE-PG-HBA.CONF"
></A
><P
><B
>Example 6-1. An example <TT
CLASS="FILENAME"
>pg_hba.conf</TT
> file</B
></P
><PRE
CLASS="PROGRAMLISTING"
># Allow any user on the local system to connect to any database under
# any user name using Unix-domain sockets (the default for local
# connections).
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
local all all trust
# The same using local loopback TCP/IP connections.
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host all all 127.0.0.1 255.255.255.255 trust
# Allow any user from any host with IP address 192.168.93.x to connect
# to database "template1" as the same user name that ident reports for
# the connection (typically the Unix user name).
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host template1 all 192.168.93.0 255.255.255.0 ident sameuser
# Allow a user from host 192.168.12.10 to connect to database
# "template1" if the user's password is correctly supplied.
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host template1 all 192.168.12.10 255.255.255.255 md5
# In the absence of preceding "host" lines, these two lines will
# reject all connection from 192.168.54.1 (since that entry will be
# matched first), but allow Kerberos V connections from anywhere else
# on the Internet. The zero mask means that no bits of the host IP
# address are considered so it matches any host.
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host all all 192.168.54.1 255.255.255.255 reject
host all all 0.0.0.0 0.0.0.0 krb5
# Allow users from 192.168.x.x hosts to connect to any database, if
# they pass the ident check. If, for example, ident says the user is
# "bryanh" and he requests to connect as PostgreSQL user "guest1", the
# connection is allowed if there is an entry in pg_ident.conf for map
# "omicron" that says "bryanh" is allowed to connect as "guest1".
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
host all all 192.168.0.0 255.255.0.0 ident omicron
# If these are the only three lines for local connections, they will
# allow local users to connect only to their own databases (databases
# with the same name as their user name) except for administrators and
# members of group "support" who may connect to all databases. The file
# $PGDATA/admins contains a list of user names. Passwords are required in
# all cases.
#
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
local sameuser all md5
local all @admins md5
local all +support md5
# The last two lines above can be combined into a single line:
local all @admins,+support md5
# The database column can also use lists and file names, but not groups:
local db1,db2,@demodbs all md5</PRE
></DIV
>
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="manage-ag-dropdb.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="auth-methods.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Destroying a Database</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="admin.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Authentication methods</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
