Wiki / Authentication Methods / Authentication and access control

radius

Authenticate using a RADIUS server. See Section 20.11 for details.

Reading PostgreSQL 18.6.

Description

Authenticate using a RADIUS server. See Section 20.11 for details.

Method: radius
Configuration: pg_hba.conf
Inventory: User-visible source authentication method

Documented method options and alternatives

Option or term	Meaning
radiusservers	The DNS names or IP addresses of the RADIUS servers to connect to. This parameter is required.
radiussecrets	The shared secrets used when talking securely to the RADIUS servers. This must have exactly the same value on the PostgreSQL and RADIUS servers. It is recommended that this be a string of at least 16 characters. This parameter is required. Note The encryption vector used will only be cryptographically strong if PostgreSQL is built with support for OpenSSL . In other cases, the transmission to the RADIUS server should only be considered obfuscated, not secured, and external security measures should be applied if necessary.
radiusports	The port numbers to connect to on the RADIUS servers. If no port is specified, the default RADIUS port ( 1812 ) will be used.
radiusidentifiers	The strings to be used as NAS Identifier in the RADIUS requests. This parameter can be used, for example, to identify which database cluster the user is attempting to connect to, which can be useful for policy matching on the RADIUS server. If no identifier is specified, the default postgresql will be used.

Manual definition

20.11. RADIUS Authentication

This authentication method operates similarly to password except that it uses RADIUS as the password verification method. RADIUS is used only to validate the user name/password pairs. Therefore the user must already exist in the database before RADIUS can be used for authentication.

When using RADIUS authentication, an Access Request message will be sent to the configured RADIUS server. This request will be of type Authenticate Only, and include parameters for user name, password (encrypted) and NAS Identifier. The request will be encrypted using a secret shared with the server. The RADIUS server will respond to this request with either Access Accept or Access Reject. There is no support for RADIUS accounting.

Multiple RADIUS servers can be specified, in which case they will be tried sequentially. If a negative response is received from a server, the authentication will fail. If no response is received, the next server in the list will be tried. To specify multiple servers, separate the server names with commas and surround the list with double quotes. If multiple servers are specified, the other RADIUS options can also be given as comma-separated lists, to provide individual values for each server. They can also be specified as a single value, in which case that value will apply to all servers.

The following configuration options are supported for RADIUS:

radiusservers: The DNS names or IP addresses of the RADIUS servers to connect to. This parameter is required.
radiussecrets: The shared secrets used when talking securely to the RADIUS servers. This must have exactly the same value on the PostgreSQL and RADIUS servers. It is recommended that this be a string of at least 16 characters. This parameter is required.

Note

The encryption vector used will only be cryptographically strong if PostgreSQL is built with support for OpenSSL. In other cases, the transmission to the RADIUS server should only be considered obfuscated, not secured, and external security measures should be applied if necessary.
radiusports: The port numbers to connect to on the RADIUS servers. If no port is specified, the default RADIUS port (1812) will be used.
radiusidentifiers: The strings to be used as NAS Identifier in the RADIUS requests. This parameter can be used, for example, to identify which database cluster the user is attempting to connect to, which can be useful for policy matching on the RADIUS server. If no identifier is specified, the default postgresql will be used.

If it is necessary to have a comma or whitespace in a RADIUS parameter value, that can be done by putting double quotes around the value, but it is tedious because two layers of double-quoting are now required. An example of putting whitespace into RADIUS secret strings is:

host ... radius radiusservers="server1,server2" radiussecrets="""secret one"",""secret two"""

Documentation and source

Source build

Version: 18.6
Build: https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2
Source fingerprint: 555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f

Compare versions

PostgreSQL 18 → 19: removed.

--- PostgreSQL 18
+++ PostgreSQL 19
@@ -1,9 +1 @@
-{
-  "documented_option_names": [
-    "radiusidentifiers",
-    "radiusports",
-    "radiussecrets",
-    "radiusservers"
-  ],
-  "method": "radius"
-}
+Not recorded in this version

Compares recorded interfaces and attributes. Source fingerprints and build metadata are excluded; an absent sample is not proof of the introduction or removal release.

Related entries

Export JSON · Back to Authentication Methods · Recorded in PostgreSQL 10 through 18; the first sample is not necessarily its introduction.