mirror of
https://github.com/postgres/postgres.git
synced 2025-07-15 19:21:59 +03:00
Add LDAP URL documentation.
Albe Laurenz
This commit is contained in:
@ -1,4 +1,4 @@
|
|||||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.243 2007/09/02 01:13:55 momjian Exp $ -->
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.244 2007/09/14 14:31:22 momjian Exp $ -->
|
||||||
|
|
||||||
<chapter id="libpq">
|
<chapter id="libpq">
|
||||||
<title><application>libpq</application> - C Library</title>
|
<title><application>libpq</application> - C Library</title>
|
||||||
@ -5085,6 +5085,19 @@ defaultNoticeProcessor(void *arg, const char *message)
|
|||||||
ldap://ldap.mycompany.com/dc=mycompany,dc=com?uniqueMember?one?(cn=mydatabase)
|
ldap://ldap.mycompany.com/dc=mycompany,dc=com?uniqueMember?one?(cn=mydatabase)
|
||||||
</synopsis>
|
</synopsis>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
You can also mix regular service file entries with LDAP lookups.
|
||||||
|
A complete example for a stanza in <filename>pg_service.conf</filename>
|
||||||
|
would be:
|
||||||
|
<synopsis>
|
||||||
|
# only host and port are stored in LDAP, specify dbname and user explicitly
|
||||||
|
[customerdb]
|
||||||
|
dbname=customer
|
||||||
|
user=appuser
|
||||||
|
ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
|
||||||
|
</synopsis>
|
||||||
|
<para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
|
||||||
|
@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.194 2007/08/22 04:45:20 tgl Exp $
|
$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.195 2007/09/14 14:31:22 momjian Exp $
|
||||||
PostgreSQL documentation
|
PostgreSQL documentation
|
||||||
-->
|
-->
|
||||||
|
|
||||||
@ -567,6 +567,8 @@ PostgreSQL documentation
|
|||||||
<programlisting>
|
<programlisting>
|
||||||
$ <userinput>psql "service=myservice sslmode=require"</userinput>
|
$ <userinput>psql "service=myservice sslmode=require"</userinput>
|
||||||
</programlisting>
|
</programlisting>
|
||||||
|
This way you can also use LDAP for connection parameter lookup as
|
||||||
|
described in <xref linkend="libpq-ldap">.
|
||||||
See <xref linkend="libpq-connect"> for more information on all the
|
See <xref linkend="libpq-connect"> for more information on all the
|
||||||
available connection options.
|
available connection options.
|
||||||
</para>
|
</para>
|
||||||
|
@ -4,7 +4,8 @@
|
|||||||
# A service is a set of named connection parameters. You may specify
|
# A service is a set of named connection parameters. You may specify
|
||||||
# multiple services in this file. Each starts with a service name in
|
# multiple services in this file. Each starts with a service name in
|
||||||
# brackets. Subsequent lines have connection configuration parameters of
|
# brackets. Subsequent lines have connection configuration parameters of
|
||||||
# the pattern "param=value". A sample configuration for postgres is
|
# the pattern "param=value" or LDAP URLs starting with "ldap://"
|
||||||
|
# to look up such parameters. A sample configuration for postgres is
|
||||||
# included in this file. Lines beginning with '#' are comments.
|
# included in this file. Lines beginning with '#' are comments.
|
||||||
#
|
#
|
||||||
# Copy this to your sysconf directory (typically /usr/local/pgsql/etc) and
|
# Copy this to your sysconf directory (typically /usr/local/pgsql/etc) and
|
||||||
|
Reference in New Issue
Block a user