pg.ddx.io pgsql-docs@postgresql.org mailing list archive help / color / mirror / Atom feed From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: pgsql-docs <pgsql-docs@postgresql.org>
Subject: authentication methods sections
Date: Wed, 11 Apr 2018 20:37:47 -0400
Message-ID: <167eeddc-c7a8-101e-10da-202ab2c2f78e@2ndquadrant.com> (raw )
I find that the section authentication methods
<https://www.postgresql.org/docs/devel/static/auth-methods.html ; is
becoming harder to read and navigate, because we keep adding
authentication methods and more information about them, and it's all on
one HTML page. I propose to move those sections up one level in the
hierarchy so they end up on separate HTML pages.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachments:
0001-doc-Restructure-authentication-methods-sections.patch (text/plain, 4.2K) download
From ef0ffbfae26a344310cd710c1249b0a8018bccee Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Wed, 11 Apr 2018 20:33:53 -0400
Subject: [PATCH] doc: Restructure authentication methods sections
Move the authentication methods sections up to sect1, so they are easier
to navigate in HTML.
---
doc/src/sgml/client-auth.sgml | 48 +++++++++++++++++------------------
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 53832d08e2..656d5f9417 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -859,10 +859,11 @@ <title>An Example <filename>pg_ident.conf</filename> File</title>
<sect1 id="auth-methods">
<title>Authentication Methods</title>
<para>
- The following subsections describe the authentication methods in more detail.
+ The following sections describe the authentication methods in more detail.
</para>
+ </sect1>
- <sect2 id="auth-trust">
+ <sect1 id="auth-trust">
<title>Trust Authentication</title>
<para>
@@ -908,9 +909,9 @@ <title>Trust Authentication</title>
for any TCP/IP connections other than those from <systemitem>localhost</systemitem> (127.0.0.1).
</para>
- </sect2>
+ </sect1>
- <sect2 id="auth-password">
+ <sect1 id="auth-password">
<title>Password Authentication</title>
<indexterm>
@@ -1038,9 +1039,9 @@ <title>Password Authentication</title>
and change the authentication method specifications
in <filename>pg_hba.conf</filename> to <literal>scram-sha-256</literal>.
</para>
- </sect2>
+ </sect1>
- <sect2 id="gssapi-auth">
+ <sect1 id="gssapi-auth">
<title>GSSAPI Authentication</title>
<indexterm zone="gssapi-auth">
@@ -1192,9 +1193,9 @@ <title>GSSAPI Authentication</title>
</varlistentry>
</variablelist>
</para>
- </sect2>
+ </sect1>
- <sect2 id="sspi-auth">
+ <sect1 id="sspi-auth">
<title>SSPI Authentication</title>
<indexterm zone="sspi-auth">
@@ -1310,9 +1311,9 @@ <title>SSPI Authentication</title>
</varlistentry>
</variablelist>
</para>
- </sect2>
+ </sect1>
- <sect2 id="auth-ident">
+ <sect1 id="auth-ident">
<title>Ident Authentication</title>
<indexterm>
@@ -1391,9 +1392,9 @@ <title>Ident Authentication</title>
since <productname>PostgreSQL</productname> does not have any way to decrypt the
returned string to determine the actual user name.
</para>
- </sect2>
+ </sect1>
- <sect2 id="auth-peer">
+ <sect1 id="auth-peer">
<title>Peer Authentication</title>
<indexterm>
@@ -1432,9 +1433,9 @@ <title>Peer Authentication</title>
and <systemitem class="osname">Solaris</systemitem>.
</para>
- </sect2>
+ </sect1>
- <sect2 id="auth-ldap">
+ <sect1 id="auth-ldap">
<title>LDAP Authentication</title>
<indexterm zone="auth-ldap">
@@ -1723,9 +1724,9 @@ <title>LDAP Authentication</title>
</para>
</tip>
- </sect2>
+ </sect1>
- <sect2 id="auth-radius">
+ <sect1 id="auth-radius">
<title>RADIUS Authentication</title>
<indexterm zone="auth-radius">
@@ -1824,9 +1825,9 @@ <title>RADIUS Authentication</title>
</variablelist>
</para>
- </sect2>
+ </sect1>
- <sect2 id="auth-cert">
+ <sect1 id="auth-cert">
<title>Certificate Authentication</title>
<indexterm zone="auth-cert">
@@ -1870,9 +1871,9 @@ <title>Certificate Authentication</title>
is a check that the <literal>cn</literal> attribute matches the database
user name.
</para>
- </sect2>
+ </sect1>
- <sect2 id="auth-pam">
+ <sect1 id="auth-pam">
<title>PAM Authentication</title>
<indexterm zone="auth-pam">
@@ -1928,9 +1929,9 @@ <title>PAM Authentication</title>
LDAP or other authentication methods.
</para>
</note>
- </sect2>
+ </sect1>
- <sect2 id="auth-bsd">
+ <sect1 id="auth-bsd">
<title>BSD Authentication</title>
<indexterm zone="auth-bsd">
@@ -1963,8 +1964,7 @@ <title>BSD Authentication</title>
exists by default on OpenBSD systems.
</para>
</note>
- </sect2>
- </sect1>
+ </sect1>
<sect1 id="client-authentication-problems">
<title>Authentication Problems</title>
--
2.17.0
view thread (3+ messages) latest in thread
Message-ID: <167eeddc-c7a8-101e-10da-202ab2c2f78e@2ndquadrant.com>
Permalink: ../167eeddc-c7a8-101e-10da-202ab2c2f78e@2ndquadrant.com/
Also on: postgresql.org/message-id/167eeddc-c7a8-101e-10da-202ab2c2f78e@2ndquadrant.com
copy link · copy postgr.es · copy git am
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com
Subject: Re: authentication methods sections
In-Reply-To: <167eeddc-c7a8-101e-10da-202ab2c2f78e@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox