require_auth
Specifies the authentication method that the client requires from the server. If the server does not use the required method to authenticate the client, or if the authentication handshake is not fully completed by the server, the connection will fail. A comma-separated list of methods may also be provided, of which the server must use exactly one in order for the connection to succeed. By default, any authentication method is accepted, and the server is free to skip authentication altogether.
当前阅读 PG 18·选择有来源记录的版本
此版本暂无所选语言的定义,以下显示原始英文内容。
- Client library
- libpq 18.6
- Manual definition
- Documented
- Source environment fallback
- PGREQUIREAUTH
- Compiled fallback expression
- NULL
- documented
- true
- environment
- map[description:PGREQUIREAUTH behaves the same as the require_auth connection parameter. name:PGREQUIREAUTH source_url:/docs/18/libpq-envars.html]
- keyword
- require_auth
- manual path
- libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH
- signature
- require_auth
版本定义 PG 18
require_auth-
Specifies the authentication method that the client requires from the server. If the server does not use the required method to authenticate the client, or if the authentication handshake is not fully completed by the server, the connection will fail. A comma-separated list of methods may also be provided, of which the server must use exactly one in order for the connection to succeed. By default, any authentication method is accepted, and the server is free to skip authentication altogether.
Methods may be negated with the addition of a
!prefix, in which case the server must not attempt the listed method; any other method is accepted, and the server is free not to authenticate the client at all. If a comma-separated list is provided, the server may not attempt any of the listed negated methods. Negated and non-negated forms may not be combined in the same setting.As a final special case, the
nonemethod requires the server not to use an authentication challenge. (It may also be negated, to require some form of authentication.)The following methods may be specified:
password-
The server must request plaintext password authentication.
md5-
The server must request MD5 hashed password authentication.
Warning
Support for MD5-encrypted passwords is deprecated and will be removed in a future release of PostgreSQL. Refer to Section 20.5 for details about migrating to another password type.
gss-
The server must either request a Kerberos handshake via GSSAPI or establish a GSS-encrypted channel (see also gssencmode).
sspi-
The server must request Windows SSPI authentication.
scram-sha-256-
The server must successfully complete a SCRAM-SHA-256 authentication exchange with the client.
oauth-
The server must request an OAuth bearer token from the client.
none-
The server must not prompt the client for an authentication exchange. (This does not prohibit client certificate authentication via TLS, nor GSS authentication via its encrypted transport.)
Environment fallback
| Variable | Documented behavior |
|---|---|
| PGREQUIREAUTH | PGREQUIREAUTH behaves the same as the require_auth connection parameter. |
比较版本
完整来源事实
default evidence
Specifies the authentication method that the client requires from the server. If the server does not use the required method to authenticate the client, or if the authentication handshake is not fully completed by the server, the connection will fail. A comma-separated list of methods may also be provided, of which the server must use exactly one in order for the connection to succeed. By default, any authentication method is accepted, and the server is free to skip authentication altogether.
precedence evidence
The following environment variables can be used to select default connection parameter values, which will be used by PQconnectdb , PQsetdbLogin and PQsetdb if no value is directly specified by the calling code. These are useful to avoid hard-coding database connection information into simple client applications, for example., Service names can be defined in either a per-user service file or a system-wide file. If the same service name exists in both the user and the system file, the user file takes precedence. By default, the per-user service file is named ~/.pg_service.conf . On Microsoft Windows, it is named %APPDATA%\postgresql\.pg_service.conf (where %APPDATA% refers to the Application Data subdirectory in the user's profile). A different file name can be specified by setting the environment variable PGSERVICEFILE . The system-wide file is named pg_service.conf . By default it is sought in the etc directory of the PostgreSQL installation (use pg_config --sysconfdir to identify this directory precisely). Another directory, but not a different file name, can be specified by setting the environment variable PGSYSCONFDIR ., Connection parameters obtained from a service file are combined with parameters obtained from other sources. A service file setting overrides the corresponding environment variable, and in turn can be overridden by a value given directly in the connection string. For example, using the above service file, a connection string service=mydb port=5434 will use host somehost , port 5434 , user admin , and other parameters as set by environment variables or built-in defaults.
source option
{"compiled_default_expression":"NULL","declaration":"\"require_auth\", \"PGREQUIREAUTH\", NULL, NULL, \"Require-Auth\", \"\", 14, offsetof(struct pg_conn, require_auth)","environment":"PGREQUIREAUTH","keyword":"require_auth","source_notes":[]}来源引用
- 18.6 English manual · libpq-connect.html
- 18.6 libpq connection option declarations
- 18.6 English manual · libpq-envars.html
- 18.6 English manual · libpq-pgservice.html
- 固定 PostgreSQL 源码归档
定义来源
center · PostgreSQL 18 · ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8
正文语言: en · ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8