Chapter 18. Client Authentication

Table of Contents
18.1. The pg_hba.conf File
18.2. User Name Maps
18.3. Authentication Methods
18.3.1. Trust Authentication
18.3.2. Password Authentication
18.3.3. GSSAPI Authentication
18.3.4. SSPI Authentication
18.3.5. Kerberos Authentication
18.3.6. Ident Authentication
18.3.7. Peer Authentication
18.3.8. LDAP Authentication
18.3.9. RADIUS Authentication
18.3.10. Certificate Authentication
18.3.11. PAM Authentication
18.4. Authentication Problems

Note: The following description applies both to Postgres-XC and PostgreSQL if not described explicitly. You can read PostgreSQL as Postgres-XC except for version number, which is specific to each product.

When a client application connects to the database server, it specifies which PostgreSQL database 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 Chapter 19 for more information. Therefore, it is essential to restrict which database users can connect.

Note: As explained in Chapter 19, PostgreSQL actually does privilege management in terms of "roles". In this chapter, we consistently use database user to mean "role with the LOGIN privilege".

Authentication 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 database user name that was requested.

PostgreSQL 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.

PostgreSQL database 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 might have many database users who have no local operating system account, and in such cases there need be no connection between database user names and OS user names.