{"Entry":{"collection":"auth","key":"radius","name":"radius","aliases":[],"metadata":{"aliases":[],"category":"Authentication and access control","content_hash":"5cc4b8389a7a6af91c11f643a942a97c92f95656c2a88a4443b205854c0b3bbb","imported_at":"2026-09-30T00:40:33.336913+08:00","name":"radius","name_zh":"","slug":"radius","summary":"Authenticate using a RADIUS server. See Section 20.11 for details."}},"Definition":{"Collection":"auth","Key":"radius","SourceDatabase":"center","Version":"18","SourceTable":"authentication_method","SourceKey":"radius","SourceRevision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","Facts":{"aliases":[],"attributes":{"configuration":"pg_hba.conf","inventory":"User-visible source authentication method","method":"radius"},"comparison_data":{"documented_option_names":["radiusidentifiers","radiusports","radiussecrets","radiusservers"],"method":"radius"},"comparison_hash":"084932634de939bfac07ac9c692a7d4dd0c6593c73dd494f2f0ccbad15d6f1a4","description":["Authenticate using a RADIUS server. See Section 20.11 for details."],"facts":[{"label":"Method","value":"radius"},{"label":"Configuration","value":"pg_hba.conf"},{"label":"Inventory","value":"User-visible source authentication method"}],"manual_html":"\u003cdiv class=\"sect1\" id=\"AUTH-RADIUS\"\u003e\n\u003cdiv class=\"titlepage\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2 class=\"title\"\u003e20.11. RADIUS Authentication \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThis authentication method operates similarly to \u003ccode class=\"literal\"\u003epassword\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eWhen using RADIUS authentication, an Access Request message will be sent to the configured RADIUS server. This request will be of type \u003ccode class=\"literal\"\u003eAuthenticate Only\u003c/code\u003e, and include parameters for \u003ccode class=\"literal\"\u003euser name\u003c/code\u003e, \u003ccode class=\"literal\"\u003epassword\u003c/code\u003e (encrypted) and \u003ccode class=\"literal\"\u003eNAS Identifier\u003c/code\u003e. The request will be encrypted using a secret shared with the server. The RADIUS server will respond to this request with either \u003ccode class=\"literal\"\u003eAccess Accept\u003c/code\u003e or \u003ccode class=\"literal\"\u003eAccess Reject\u003c/code\u003e. There is no support for RADIUS accounting.\u003c/p\u003e\n\u003cp\u003eMultiple 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.\u003c/p\u003e\n\u003cp\u003eThe following configuration options are supported for RADIUS:\u003c/p\u003e\n\u003cdiv class=\"variablelist\"\u003e\n\u003cdl class=\"variablelist\"\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003eradiusservers\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe DNS names or IP addresses of the RADIUS servers to connect to. This parameter is required.\u003c/p\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003eradiussecrets\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e\n\u003cdiv class=\"note\"\u003e\n\u003ch3 class=\"title\"\u003eNote\u003c/h3\u003e\n\u003cp\u003eThe encryption vector used will only be cryptographically strong if \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e is built with support for \u003cspan class=\"productname\"\u003eOpenSSL\u003c/span\u003e. 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.\u003c/p\u003e\n\u003c/div\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003eradiusports\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe port numbers to connect to on the RADIUS servers. If no port is specified, the default RADIUS port (\u003ccode class=\"literal\"\u003e1812\u003c/code\u003e) will be used.\u003c/p\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003eradiusidentifiers\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe strings to be used as \u003ccode class=\"literal\"\u003eNAS Identifier\u003c/code\u003e 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 \u003ccode class=\"literal\"\u003epostgresql\u003c/code\u003e will be used.\u003c/p\u003e\n\u003c/dd\u003e\n\u003c/dl\u003e\n\u003c/div\u003e\n\u003cp\u003eIf 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:\u003c/p\u003e\n\u003cpre class=\"programlisting\"\u003ehost ... radius radiusservers=\"server1,server2\" radiussecrets=\"\"\"secret one\"\",\"\"secret two\"\"\"\n\u003c/pre\u003e\n\u003c/div\u003e","manual_path":"/docs/18/auth-radius.html","related":[],"release":{"catalog_fingerprint":"65c93d6048ef30e61023a84f9680fa6a92b1c383b7eb226741170077eb078502","channel":"stable","label":"18.6","major":"18","ref":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","revision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"},"sections":[],"signature":"","sources":[{"label":"Matching PostgreSQL source archive","sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","url":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2"},{"label":"PostgreSQL 18 English manual","path":"auth-radius.html","sha256":"adc663bf8e300c937cc9ee1b2004b31455391ad8d8699f75abe1f643cc7ff39b","url":"/docs/18/auth-radius.html"},{"label":"PostgreSQL 18 English manual","path":"auth-pg-hba-conf.html","sha256":"6340d4abea2e0a3482afc31bcd1599a0fa10dc28a6f1e05d79ba831e2dd0b4c9","url":"/docs/18/auth-pg-hba-conf.html"}],"tables":[{"columns":[{"key":"name","label":"Option or term"},{"key":"description","label":"Meaning"}],"key":"method-options","rows":[{"description":"The DNS names or IP addresses of the RADIUS servers to connect to. This parameter is required.","name":"radiusservers"},{"description":"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.","name":"radiussecrets"},{"description":"The port numbers to connect to on the RADIUS servers. If no port is specified, the default RADIUS port ( 1812 ) will be used.","name":"radiusports"},{"description":"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.","name":"radiusidentifiers"}],"title":"Documented method options and alternatives"}]},"ManualEvidence":{"manual_path":"/docs/18/auth-radius.html","release":{"catalog_fingerprint":"65c93d6048ef30e61023a84f9680fa6a92b1c383b7eb226741170077eb078502","channel":"stable","label":"18.6","major":"18","ref":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","revision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"},"sources":[{"label":"Matching PostgreSQL source archive","sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","url":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2"},{"label":"PostgreSQL 18 English manual","path":"auth-radius.html","sha256":"adc663bf8e300c937cc9ee1b2004b31455391ad8d8699f75abe1f643cc7ff39b","url":"/docs/18/auth-radius.html"},{"label":"PostgreSQL 18 English manual","path":"auth-pg-hba-conf.html","sha256":"6340d4abea2e0a3482afc31bcd1599a0fa10dc28a6f1e05d79ba831e2dd0b4c9","url":"/docs/18/auth-pg-hba-conf.html"}]},"MeasuredEvidence":{}},"Text":{"Collection":"auth","Key":"radius","SourceDatabase":"center","Version":"18","Locale":"en","Title":"radius","Summary":"Authenticate using a RADIUS server. See Section 20.11 for details.","BodyHTML":"\u003cdiv id=\"AUTH-RADIUS\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2\u003e20.11. RADIUS Authentication \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThis authentication method operates similarly to \u003ccode\u003epassword\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eWhen using RADIUS authentication, an Access Request message will be sent to the configured RADIUS server. This request will be of type \u003ccode\u003eAuthenticate Only\u003c/code\u003e, and include parameters for \u003ccode\u003euser name\u003c/code\u003e, \u003ccode\u003epassword\u003c/code\u003e (encrypted) and \u003ccode\u003eNAS Identifier\u003c/code\u003e. The request will be encrypted using a secret shared with the server. The RADIUS server will respond to this request with either \u003ccode\u003eAccess Accept\u003c/code\u003e or \u003ccode\u003eAccess Reject\u003c/code\u003e. There is no support for RADIUS accounting.\u003c/p\u003e\n\u003cp\u003eMultiple 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.\u003c/p\u003e\n\u003cp\u003eThe following configuration options are supported for RADIUS:\u003c/p\u003e\n\u003cdiv\u003e\n\u003cdl\u003e\n\u003cdt\u003e\u003cspan\u003e\u003ccode\u003eradiusservers\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe DNS names or IP addresses of the RADIUS servers to connect to. This parameter is required.\u003c/p\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan\u003e\u003ccode\u003eradiussecrets\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e\n\u003cdiv\u003e\n\u003ch3\u003eNote\u003c/h3\u003e\n\u003cp\u003eThe encryption vector used will only be cryptographically strong if \u003cspan\u003ePostgreSQL\u003c/span\u003e is built with support for \u003cspan\u003eOpenSSL\u003c/span\u003e. 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.\u003c/p\u003e\n\u003c/div\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan\u003e\u003ccode\u003eradiusports\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe port numbers to connect to on the RADIUS servers. If no port is specified, the default RADIUS port (\u003ccode\u003e1812\u003c/code\u003e) will be used.\u003c/p\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan\u003e\u003ccode\u003eradiusidentifiers\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe strings to be used as \u003ccode\u003eNAS Identifier\u003c/code\u003e 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 \u003ccode\u003epostgresql\u003c/code\u003e will be used.\u003c/p\u003e\n\u003c/dd\u003e\n\u003c/dl\u003e\n\u003c/div\u003e\n\u003cp\u003eIf 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:\u003c/p\u003e\n\u003cpre\u003ehost ... radius radiusservers=\u0026#34;server1,server2\u0026#34; radiussecrets=\u0026#34;\u0026#34;\u0026#34;secret one\u0026#34;\u0026#34;,\u0026#34;\u0026#34;secret two\u0026#34;\u0026#34;\u0026#34;\n\u003c/pre\u003e\n\u003c/div\u003e","SourceRevision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","ContentHash":"ef1f688b506e7b5c1afcea42ac36bc8da01504f03195a7050d610789931b15ea","Payload":{"description":["Authenticate using a RADIUS server. See Section 20.11 for details."],"manual_html":"\u003cdiv class=\"sect1\" id=\"AUTH-RADIUS\"\u003e\n\u003cdiv class=\"titlepage\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2 class=\"title\"\u003e20.11. RADIUS Authentication \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThis authentication method operates similarly to \u003ccode class=\"literal\"\u003epassword\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eWhen using RADIUS authentication, an Access Request message will be sent to the configured RADIUS server. This request will be of type \u003ccode class=\"literal\"\u003eAuthenticate Only\u003c/code\u003e, and include parameters for \u003ccode class=\"literal\"\u003euser name\u003c/code\u003e, \u003ccode class=\"literal\"\u003epassword\u003c/code\u003e (encrypted) and \u003ccode class=\"literal\"\u003eNAS Identifier\u003c/code\u003e. The request will be encrypted using a secret shared with the server. The RADIUS server will respond to this request with either \u003ccode class=\"literal\"\u003eAccess Accept\u003c/code\u003e or \u003ccode class=\"literal\"\u003eAccess Reject\u003c/code\u003e. There is no support for RADIUS accounting.\u003c/p\u003e\n\u003cp\u003eMultiple 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.\u003c/p\u003e\n\u003cp\u003eThe following configuration options are supported for RADIUS:\u003c/p\u003e\n\u003cdiv class=\"variablelist\"\u003e\n\u003cdl class=\"variablelist\"\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003eradiusservers\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe DNS names or IP addresses of the RADIUS servers to connect to. This parameter is required.\u003c/p\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003eradiussecrets\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e\n\u003cdiv class=\"note\"\u003e\n\u003ch3 class=\"title\"\u003eNote\u003c/h3\u003e\n\u003cp\u003eThe encryption vector used will only be cryptographically strong if \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e is built with support for \u003cspan class=\"productname\"\u003eOpenSSL\u003c/span\u003e. 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.\u003c/p\u003e\n\u003c/div\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003eradiusports\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe port numbers to connect to on the RADIUS servers. If no port is specified, the default RADIUS port (\u003ccode class=\"literal\"\u003e1812\u003c/code\u003e) will be used.\u003c/p\u003e\n\u003c/dd\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003eradiusidentifiers\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eThe strings to be used as \u003ccode class=\"literal\"\u003eNAS Identifier\u003c/code\u003e 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 \u003ccode class=\"literal\"\u003epostgresql\u003c/code\u003e will be used.\u003c/p\u003e\n\u003c/dd\u003e\n\u003c/dl\u003e\n\u003c/div\u003e\n\u003cp\u003eIf 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:\u003c/p\u003e\n\u003cpre class=\"programlisting\"\u003ehost ... radius radiusservers=\"server1,server2\" radiussecrets=\"\"\"secret one\"\",\"\"secret two\"\"\"\n\u003c/pre\u003e\n\u003c/div\u003e","related":[],"sections":[],"tables":[{"columns":[{"key":"name","label":"Option or term"},{"key":"description","label":"Meaning"}],"key":"method-options","rows":[{"description":"The DNS names or IP addresses of the RADIUS servers to connect to. This parameter is required.","name":"radiusservers"},{"description":"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.","name":"radiussecrets"},{"description":"The port numbers to connect to on the RADIUS servers. If no port is specified, the default RADIUS port ( 1812 ) will be used.","name":"radiusports"},{"description":"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.","name":"radiusidentifiers"}],"title":"Documented method options and alternatives"}]}},"RequestedLocale":"zh-Hans","Fallback":true,"Versions":["10","11","12","13","14","15","16","17","18"],"Locales":["en"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}