{"Entry":{"collection":"auth","key":"ident","name":"ident","aliases":[],"metadata":{"aliases":[],"category":"Authentication and access control","content_hash":"24a6051c3372fa1d95cd853b527cbb4c91ef741cb1c356020f49f774bbc717b1","derived_content_hash":"89ccb58d72bfc2a8d1c3932d783d82d607859de551555993c7ad3597aa287735","imported_at":"2026-09-30T00:40:33.290455+08:00","name":"ident","name_zh":"","slug":"ident","summary":"Obtain the operating system user name of the client by contacting the ident server on the client and check if it matches the requested database user name. Ident authentication can only be used on TCP/IP connections. When specified for local connections, peer authentication will be used instead. See Section 20.8 for details."}},"Definition":{"Collection":"auth","Key":"ident","SourceDatabase":"center","Version":"18","SourceTable":"authentication_method","SourceKey":"ident","SourceRevision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","Facts":{"aliases":[],"attributes":{"configuration":"pg_hba.conf","inventory":"User-visible source authentication method","method":"ident"},"comparison_data":{"documented_option_names":["map"],"method":"ident"},"comparison_hash":"1e75b0772a935e648eb3675daa207e7e3b87b3ee5ae88c48a8eb96b82f094fc0","description":["Obtain the operating system user name of the client by contacting the ident server on the client and check if it matches the requested database user name. Ident authentication can only be used on TCP/IP connections. When specified for local connections, peer authentication will be used instead. See Section 20.8 for details."],"description_zh":"认证方法 ident。","description_zh_html":"\u003cp\u003e认证方法 ident。\u003c/p\u003e\u003cdl\u003e\u003cdt\u003e索引访问方法\u003c/dt\u003e\u003cdd\u003e\u003ccode\u003eident\u003c/code\u003e\u003c/dd\u003e\u003cdt\u003e配置\u003c/dt\u003e\u003cdd\u003e\u003ccode\u003epg_hba.conf\u003c/code\u003e\u003c/dd\u003e\u003c/dl\u003e\u003ch3\u003e同版本中文手册节选\u003c/h3\u003e\u003cp\u003e\n    ident 认证方法通过从一个 ident 服务器获得客户端的操作系统用户名并且用它作为被允许的数据库用户名（和可选的用户名映射）来工作。它只在 TCP/IP 连接上支持。\n   \u003c/p\u003e\u003cp\u003e\n\u003ccode class=\"literal\"\u003eident\u003c/code\u003e 支持下列配置选项：\n    \u003c/p\u003e\u003cp\u003e\n\u003cspan class=\"quote\"\u003e“\u003cspan class=\"quote\"\u003e标识协议\u003c/span\u003e”\u003c/span\u003e在\n    \u003ca class=\"ulink\" href=\"https://datatracker.ietf.org/doc/html/rfc1413\"\u003eRFC 1413\u003c/a\u003e 中有描述。几乎每个类 Unix 的操作系统都默认安装了一个 ident 服务器，监听 TCP\n    端口 113。ident 服务器的基本功能是回答类似于\u003cspan class=\"quote\"\u003e“\u003cspan class=\"quote\"\u003e哪个用户发起了从你的端口 \u003cem class=\"replaceable\"\u003e\u003ccode\u003eX\u003c/code\u003e\u003c/em\u003e 到我的端口 \u003cem class=\"replaceable\"\u003e\u003ccode\u003eY\u003c/code\u003e\u003c/em\u003e 的连接？\u003c/span\u003e”\u003c/span\u003e这样的问题。由于 \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e 在建立物理连接时知道 \u003cem class=\"replaceable\"\u003e\u003ccode\u003eX\u003c/code\u003e\u003c/em\u003e 和\n    \u003cem class=\"replaceable\"\u003e\u003ccode\u003eY\u003c/code\u003e\u003c/em\u003e，它可以查询连接客户端主机上的 ident 服务器，理论上可以确定任何给定连接的操作系统用户。\n\u003c/p\u003e\u003cp\u003e\n    这个过程的缺点在于它依赖客户端本身的可信性：如果客户端机器不可信或者已被攻破，攻击者几乎可以在 113 端口上运行任何程序，并返回任意他们选择的用户名。因此，这种认证方法只适用于封闭网络，在这类网络中每台客户端机器都受到严格控制，而且数据库管理员与系统管理员之间保持密切协作。换句话说，你必须信任运行 ident 服务器的那台机器。请注意下面的警告：\n    \u003c/p\u003e\u003cp\u003e\u003ca href=\"/zh/docs/18/auth-ident.html\"\u003e查看完整中文手册与上下文\u003c/a\u003e。\u003c/p\u003e","facts":[{"label":"Method","value":"ident"},{"label":"Configuration","value":"pg_hba.conf"},{"label":"Inventory","value":"User-visible source authentication method"}],"facts_zh":[{"label":"方法","value":"ident"},{"label":"配置","value":"pg_hba.conf"},{"label":"清单","value":"用户可见的源码认证方法"}],"manual_html":"\u003cdiv class=\"sect1\" id=\"AUTH-IDENT\"\u003e\n\u003cdiv class=\"titlepage\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2 class=\"title\"\u003e20.8. Ident Authentication \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThe ident authentication method works by obtaining the client's operating system user name from an ident server and using it as the allowed database user name (with an optional user name mapping). This is only supported on TCP/IP connections.\u003c/p\u003e\n\u003cdiv class=\"note\"\u003e\n\u003ch3 class=\"title\"\u003eNote\u003c/h3\u003e\n\u003cp\u003eWhen ident is specified for a local (non-TCP/IP) connection, peer authentication (see \u003ca class=\"xref\" href=\"/docs/18/auth-peer.html\" title=\"20.9. Peer Authentication\"\u003eSection 20.9\u003c/a\u003e) will be used instead.\u003c/p\u003e\n\u003c/div\u003e\n\u003cp\u003eThe following configuration options are supported for \u003ccode class=\"literal\"\u003eident\u003c/code\u003e:\u003c/p\u003e\n\u003cdiv class=\"variablelist\"\u003e\n\u003cdl class=\"variablelist\"\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003emap\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eAllows for mapping between system and database user names. See \u003ca class=\"xref\" href=\"/docs/18/auth-username-maps.html\" title=\"20.2. User Name Maps\"\u003eSection 20.2\u003c/a\u003e for details.\u003c/p\u003e\n\u003c/dd\u003e\n\u003c/dl\u003e\n\u003c/div\u003e\n\u003cp\u003eThe \u003cspan class=\"quote\"\u003e“\u003cspan class=\"quote\"\u003eIdentification Protocol\u003c/span\u003e”\u003c/span\u003e is described in \u003ca class=\"ulink\" href=\"https://datatracker.ietf.org/doc/html/rfc1413\"\u003eRFC 1413\u003c/a\u003e. Virtually every Unix-like operating system ships with an ident server that listens on TCP port 113 by default. The basic functionality of an ident server is to answer questions like \u003cspan class=\"quote\"\u003e“\u003cspan class=\"quote\"\u003eWhat user initiated the connection that goes out of your port \u003cem class=\"replaceable\"\u003e\u003ccode\u003eX\u003c/code\u003e\u003c/em\u003e and connects to my port \u003cem class=\"replaceable\"\u003e\u003ccode\u003eY\u003c/code\u003e\u003c/em\u003e?\u003c/span\u003e”\u003c/span\u003e. Since \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e knows both \u003cem class=\"replaceable\"\u003e\u003ccode\u003eX\u003c/code\u003e\u003c/em\u003e and \u003cem class=\"replaceable\"\u003e\u003ccode\u003eY\u003c/code\u003e\u003c/em\u003e when a physical connection is established, it can interrogate the ident server on the host of the connecting client and can theoretically determine the operating system user for any given connection.\u003c/p\u003e\n\u003cp\u003eThe drawback of this procedure is that it depends on the integrity of the client: if the client machine is untrusted or compromised, an attacker could run just about any program on port 113 and return any user name they choose. This authentication method is therefore only appropriate for closed networks where each client machine is under tight control and where the database and system administrators operate in close contact. In other words, you must trust the machine running the ident server. Heed the warning:\u003c/p\u003e\n\u003cdiv class=\"blockquote\"\u003e\n\u003ctable class=\"blockquote\"\u003e\n\u003ctbody\u003e\u003ctr\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003ctd\u003e\n\u003cp\u003eThe Identification Protocol is not intended as an authorization or access control protocol.\u003c/p\u003e\n\u003c/td\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003ctd colspan=\"2\"\u003e--\u003cspan class=\"attribution\"\u003eRFC 1413\u003c/span\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\u003c/table\u003e\n\u003c/div\u003e\n\u003cp\u003eSome ident servers have a nonstandard option that causes the returned user name to be encrypted, using a key that only the originating machine's administrator knows. This option \u003cspan class=\"emphasis\"\u003e\u003cem\u003emust not\u003c/em\u003e\u003c/span\u003e be used when using the ident server with \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e, since \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e does not have any way to decrypt the returned string to determine the actual user name.\u003c/p\u003e\n\u003c/div\u003e","manual_path":"/docs/18/auth-ident.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":[],"sections_zh":[],"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-ident.html","sha256":"14dd74aab7c9cfa7b89f8873f997df364d665097bb9be19146de6d2ea45eec7c","url":"/docs/18/auth-ident.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":"Allows for mapping between system and database user names. See Section 20.2 for details.","name":"map"}],"title":"Documented method options and alternatives"}],"tables_zh":[{"columns":[{"key":"name","label":"选项或术语"},{"key":"description","label":"含义"}],"key":"method-options","rows":[{"description":"允许在系统用户名和数据库用户名之间进行映射。详见 第 20.2 节 。","name":"map"}],"title":"手册中的方法选项与替代方式"}],"zh_from":{"authored_translation":"source-derived-structured-summary","body_sha256":"5f6d147087232b2cf35daaea7e66a678a4ee1123836f005a32e0773e2890a13e","kind":"same-version-chinese-manual-with-source-derived-structured-summary","manual":{"anchor":"","build_id":107,"extraction":"concept-introduction","fragment_sha256":"8e77c0bdb1c777e21c01f9c6964b6336b4a1fb1194a452e3a9fe8791a4fbdfb3","locale":"zh-Hans","page_key":"auth-ident.html","source_hash":"0d58eab9201c93fa2ab7b41665cebdcf38c19e255966d3166b6c32be14110d6c","source_revision":"unknown:rendered-translation-baseline","translated_from_revision":null,"translation_revision":"git:b1b500221dbe5437cfca004d6b04d3f6e422765d;html-sha256:08e987a66af27b98444a8057c256314eafa13611a3fb9e888214fc436824244b","url":"/zh/docs/18/auth-ident.html","version":"18"},"runtime_rerun":false,"source_facts_revision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"}},"ManualEvidence":{"manual_path":"/docs/18/auth-ident.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-ident.html","sha256":"14dd74aab7c9cfa7b89f8873f997df364d665097bb9be19146de6d2ea45eec7c","url":"/docs/18/auth-ident.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":"ident","SourceDatabase":"center","Version":"18","Locale":"en","Title":"ident","Summary":"Obtain the operating system user name of the client by contacting the ident server on the client and check if it matches the requested database user name. Ident authentication can only be used on TCP/IP connections. When specified for local connections, peer authentication will be used instead. See Section 20.8 for details.","BodyHTML":"\u003cdiv id=\"AUTH-IDENT\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2\u003e20.8. Ident Authentication \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThe ident authentication method works by obtaining the client\u0026#39;s operating system user name from an ident server and using it as the allowed database user name (with an optional user name mapping). This is only supported on TCP/IP connections.\u003c/p\u003e\n\u003cdiv\u003e\n\u003ch3\u003eNote\u003c/h3\u003e\n\u003cp\u003eWhen ident is specified for a local (non-TCP/IP) connection, peer authentication (see \u003ca href=\"/docs/18/auth-peer.html\" rel=\"nofollow\"\u003eSection 20.9\u003c/a\u003e) will be used instead.\u003c/p\u003e\n\u003c/div\u003e\n\u003cp\u003eThe following configuration options are supported for \u003ccode\u003eident\u003c/code\u003e:\u003c/p\u003e\n\u003cdiv\u003e\n\u003cdl\u003e\n\u003cdt\u003e\u003cspan\u003e\u003ccode\u003emap\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eAllows for mapping between system and database user names. See \u003ca href=\"/docs/18/auth-username-maps.html\" rel=\"nofollow\"\u003eSection 20.2\u003c/a\u003e for details.\u003c/p\u003e\n\u003c/dd\u003e\n\u003c/dl\u003e\n\u003c/div\u003e\n\u003cp\u003eThe \u003cspan\u003e“\u003cspan\u003eIdentification Protocol\u003c/span\u003e”\u003c/span\u003e is described in \u003ca href=\"https://datatracker.ietf.org/doc/html/rfc1413\" rel=\"nofollow\"\u003eRFC 1413\u003c/a\u003e. Virtually every Unix-like operating system ships with an ident server that listens on TCP port 113 by default. The basic functionality of an ident server is to answer questions like \u003cspan\u003e“\u003cspan\u003eWhat user initiated the connection that goes out of your port \u003cem\u003e\u003ccode\u003eX\u003c/code\u003e\u003c/em\u003e and connects to my port \u003cem\u003e\u003ccode\u003eY\u003c/code\u003e\u003c/em\u003e?\u003c/span\u003e”\u003c/span\u003e. Since \u003cspan\u003ePostgreSQL\u003c/span\u003e knows both \u003cem\u003e\u003ccode\u003eX\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003eY\u003c/code\u003e\u003c/em\u003e when a physical connection is established, it can interrogate the ident server on the host of the connecting client and can theoretically determine the operating system user for any given connection.\u003c/p\u003e\n\u003cp\u003eThe drawback of this procedure is that it depends on the integrity of the client: if the client machine is untrusted or compromised, an attacker could run just about any program on port 113 and return any user name they choose. This authentication method is therefore only appropriate for closed networks where each client machine is under tight control and where the database and system administrators operate in close contact. In other words, you must trust the machine running the ident server. Heed the warning:\u003c/p\u003e\n\u003cdiv\u003e\n\u003ctable\u003e\n\u003ctbody\u003e\u003ctr\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003ctd\u003e\n\u003cp\u003eThe Identification Protocol is not intended as an authorization or access control protocol.\u003c/p\u003e\n\u003c/td\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003ctd colspan=\"2\"\u003e--\u003cspan\u003eRFC 1413\u003c/span\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\u003c/table\u003e\n\u003c/div\u003e\n\u003cp\u003eSome ident servers have a nonstandard option that causes the returned user name to be encrypted, using a key that only the originating machine\u0026#39;s administrator knows. This option \u003cspan\u003e\u003cem\u003emust not\u003c/em\u003e\u003c/span\u003e be used when using the ident server with \u003cspan\u003ePostgreSQL\u003c/span\u003e, since \u003cspan\u003ePostgreSQL\u003c/span\u003e does not have any way to decrypt the returned string to determine the actual user name.\u003c/p\u003e\n\u003c/div\u003e","SourceRevision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","ContentHash":"2c80bfee17b14ef41ab04ce673d6d3c3ebee1470004e79ba462f5936ec7d70ac","Payload":{"description":["Obtain the operating system user name of the client by contacting the ident server on the client and check if it matches the requested database user name. Ident authentication can only be used on TCP/IP connections. When specified for local connections, peer authentication will be used instead. See Section 20.8 for details."],"manual_html":"\u003cdiv class=\"sect1\" id=\"AUTH-IDENT\"\u003e\n\u003cdiv class=\"titlepage\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2 class=\"title\"\u003e20.8. Ident Authentication \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThe ident authentication method works by obtaining the client's operating system user name from an ident server and using it as the allowed database user name (with an optional user name mapping). This is only supported on TCP/IP connections.\u003c/p\u003e\n\u003cdiv class=\"note\"\u003e\n\u003ch3 class=\"title\"\u003eNote\u003c/h3\u003e\n\u003cp\u003eWhen ident is specified for a local (non-TCP/IP) connection, peer authentication (see \u003ca class=\"xref\" href=\"/docs/18/auth-peer.html\" title=\"20.9. Peer Authentication\"\u003eSection 20.9\u003c/a\u003e) will be used instead.\u003c/p\u003e\n\u003c/div\u003e\n\u003cp\u003eThe following configuration options are supported for \u003ccode class=\"literal\"\u003eident\u003c/code\u003e:\u003c/p\u003e\n\u003cdiv class=\"variablelist\"\u003e\n\u003cdl class=\"variablelist\"\u003e\n\u003cdt\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003emap\u003c/code\u003e\u003c/span\u003e\u003c/dt\u003e\n\u003cdd\u003e\n\u003cp\u003eAllows for mapping between system and database user names. See \u003ca class=\"xref\" href=\"/docs/18/auth-username-maps.html\" title=\"20.2. User Name Maps\"\u003eSection 20.2\u003c/a\u003e for details.\u003c/p\u003e\n\u003c/dd\u003e\n\u003c/dl\u003e\n\u003c/div\u003e\n\u003cp\u003eThe \u003cspan class=\"quote\"\u003e“\u003cspan class=\"quote\"\u003eIdentification Protocol\u003c/span\u003e”\u003c/span\u003e is described in \u003ca class=\"ulink\" href=\"https://datatracker.ietf.org/doc/html/rfc1413\"\u003eRFC 1413\u003c/a\u003e. Virtually every Unix-like operating system ships with an ident server that listens on TCP port 113 by default. The basic functionality of an ident server is to answer questions like \u003cspan class=\"quote\"\u003e“\u003cspan class=\"quote\"\u003eWhat user initiated the connection that goes out of your port \u003cem class=\"replaceable\"\u003e\u003ccode\u003eX\u003c/code\u003e\u003c/em\u003e and connects to my port \u003cem class=\"replaceable\"\u003e\u003ccode\u003eY\u003c/code\u003e\u003c/em\u003e?\u003c/span\u003e”\u003c/span\u003e. Since \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e knows both \u003cem class=\"replaceable\"\u003e\u003ccode\u003eX\u003c/code\u003e\u003c/em\u003e and \u003cem class=\"replaceable\"\u003e\u003ccode\u003eY\u003c/code\u003e\u003c/em\u003e when a physical connection is established, it can interrogate the ident server on the host of the connecting client and can theoretically determine the operating system user for any given connection.\u003c/p\u003e\n\u003cp\u003eThe drawback of this procedure is that it depends on the integrity of the client: if the client machine is untrusted or compromised, an attacker could run just about any program on port 113 and return any user name they choose. This authentication method is therefore only appropriate for closed networks where each client machine is under tight control and where the database and system administrators operate in close contact. In other words, you must trust the machine running the ident server. Heed the warning:\u003c/p\u003e\n\u003cdiv class=\"blockquote\"\u003e\n\u003ctable class=\"blockquote\"\u003e\n\u003ctbody\u003e\u003ctr\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003ctd\u003e\n\u003cp\u003eThe Identification Protocol is not intended as an authorization or access control protocol.\u003c/p\u003e\n\u003c/td\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e \u003c/td\u003e\n\u003ctd colspan=\"2\"\u003e--\u003cspan class=\"attribution\"\u003eRFC 1413\u003c/span\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\u003c/table\u003e\n\u003c/div\u003e\n\u003cp\u003eSome ident servers have a nonstandard option that causes the returned user name to be encrypted, using a key that only the originating machine's administrator knows. This option \u003cspan class=\"emphasis\"\u003e\u003cem\u003emust not\u003c/em\u003e\u003c/span\u003e be used when using the ident server with \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e, since \u003cspan class=\"productname\"\u003ePostgreSQL\u003c/span\u003e does not have any way to decrypt the returned string to determine the actual user name.\u003c/p\u003e\n\u003c/div\u003e","related":[],"sections":[],"tables":[{"columns":[{"key":"name","label":"Option or term"},{"key":"description","label":"Meaning"}],"key":"method-options","rows":[{"description":"Allows for mapping between system and database user names. See Section 20.2 for details.","name":"map"}],"title":"Documented method options and alternatives"}]}},"RequestedLocale":"en","Fallback":false,"Versions":["10","11","12","13","14","15","16","17","18","19","20"],"Locales":["en","zh-Hans"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}