From f04ee7043bc5a187932c2fc647abe41d3ac1d0ba Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 22 Mar 2009 21:55:07 +0000
Subject: [PATCH] Clarify 'cert' authentication documention.
---
doc/src/sgml/client-auth.sgml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 029bfd4566..097c426fd6 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.118 2009/01/09 10:13:18 mha Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.119 2009/03/22 21:55:07 momjian Exp $ -->
<chapter id="client-authentication">
<title>Client Authentication</title>
@@ -1245,9 +1245,9 @@ ldapserver=ldap.example.net prefix="cn=" suffix="dc=example, dc=net"
When using this authentication method, the server will require that
the client provide a certificate. No password prompt will be sent
to the client. The <literal>cn</literal> attribute of the certificate
- will be matched with the username the user is trying to log in as,
- and if they match the login will be allowed. Username mapping can be
- used if the usernames don't match.
+ will be matched with the login username, and if they match the
+ login will be allowed. Username mapping can be used if the usernames
+ don't match.
</para>
</sect2>