Update docs mentioning PAM doesn't work reading /etc/passwd because of
non-root. Dhanaraj M
This commit is contained in:
parent
a8c2282fe8
commit
ea63bf6ac8
@ -1,4 +1,4 @@
|
|||||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.104 2007/11/14 14:25:55 mha Exp $ -->
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.105 2007/12/29 04:15:38 momjian Exp $ -->
|
||||||
|
|
||||||
<chapter id="client-authentication">
|
<chapter id="client-authentication">
|
||||||
<title>Client Authentication</title>
|
<title>Client Authentication</title>
|
||||||
@ -1079,11 +1079,10 @@ ldap[<replaceable>s</>]://<replaceable>servername</>[:<replaceable>port</>]/<rep
|
|||||||
|
|
||||||
<note>
|
<note>
|
||||||
<para>
|
<para>
|
||||||
PAM does work authenticating against Unix system authentication
|
If PAM is set up to read <filename>/etc/shadow</>, authentication
|
||||||
because the postgres server is started by a non-root user. In order
|
will fail because the PostgreSQL server is started by a non-root
|
||||||
to enable this functionality, the root user must provide additional
|
user. However, this is not an issue with LDAP or other authentication
|
||||||
permissions to the postgres user (for reading
|
methods.
|
||||||
<filename>/etc/shadow</>).
|
|
||||||
</para>
|
</para>
|
||||||
</note>
|
</note>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user