From ead1317894acc993d779c35d2ad5d2a6e13a13fe Mon Sep 17 00:00:00 2001
From: MikeMannix <MikeMannix>
Date: Sun, 2 Sep 2001 05:32:08 +0000
Subject: [PATCH] none

---
 TWiki/TWikiUserAuthentication.mdwn | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/TWiki/TWikiUserAuthentication.mdwn b/TWiki/TWikiUserAuthentication.mdwn
index d76f818..6775f82 100644
--- a/TWiki/TWikiUserAuthentication.mdwn
+++ b/TWiki/TWikiUserAuthentication.mdwn
@@ -1,6 +1,7 @@
 <div>
   <ul>
     <li><a href="#TWiki User Authentication"> TWiki User Authentication</a><ul>
+        <li><a href="#Overview"> Overview</a></li>
         <li><a href="#Authentication Options"> Authentication Options</a></li>
         <li><a href="#Tracking by IP Address"> Tracking by IP Address</a></li>
         <li><a href="#TWiki Username vs. Login Usernam"> TWiki Username vs. Login Username</a></li>
@@ -11,7 +12,11 @@
 
 ## <a name="TWiki User Authentication"></a> TWiki User Authentication
 
-TWiki does not authenticate users internally, it depends on the <code>**REMOTE\_USER**</code> environment variable. This variable is set when you enable basic authentication or authentication via SSL (https protocol).
+Controlling TWiki site access and logging authorized user activity
+
+### <a name="Overview"></a> Overview
+
+TWiki does not authenticate users internally, it depends on the <code>**REMOTE\_USER**</code> environment variable. This variable is set when you enable Basic Authentication (.htaccess) or SSL "secure server" authentication (https protocol).
 
 TWiki uses visitor identification to keep track of who made changes to topics at what time and to manage a wide range of personal site settings. This gives a complete audit trail of changes and activity.
 
@@ -19,15 +24,15 @@ TWiki uses visitor identification to keep track of who made changes to topics at
 
 No special installation steps need to be performed if the server is already authenticated. If not, you have three remaining options to controlling user access:
 
-1. **Forget about authentication.** All changes are registered to [[TWikiGuest]] user, so you can't tell who made changes. Your site is completely open and public.
-2. **Use Basic Authentication** for the <code>**edit**</code> and <code>**attach**</code> scripts. This uses .htaccess and generates the familiar grey log-in window. [[TWiki Installation Notes|Main/TWikiDocumentation#TWiki_Installation_Notes]] has more.
+1. **Forget about authentication.** All changes are registered to [[TWikiGuest]] user, so you can't tell who made changes. Your site is completely open and public - anyone can browse and edit freely, in classic Wiki mode.<br />
+2. **Use Basic Authentication** for the <code>**edit**</code> and <code>**attach**</code> scripts. This uses .htaccess and generates the familiar grey log-in window. The [[TWiki Installation Guide|Main/TWikiDocumentation#TWiki_Installation_Notes]] has step-by-step instructions.<br />
 3. **Use SSL** to authenticate and secure the whole server.
 
 ### <a name="Tracking by IP Address"></a> Tracking by IP Address
 
 The <code>**REMOTE\_USER**</code> environment variable is only set for the scripts that are under authentication. If, for example, the <code>**edit**</code>, <code>**save**</code> and <code>**preview**</code> scripts are authenticated, but not <code>**view**</code>, you would get your [[WikiName]] in <code>**preview**</code> for the <code>**%WIKIUSERNAME%**</code> variable, but <code>**view**</code> will show <code>**TWikiGuest**</code> instead of your WikiName.
 
-There is a way to tell TWiki to remember the user for the scripts that are not authenticated, ex: in case the <code>**REMOTE\_USER**</code> environment variable is not set. TWiki can be configured to remember the IP address/username pair whenever an authentication happens (edit topic, attach file). Once remembered, the non-authenticated scripts like <code>**view**</code> will show the correct username instead of <code>**TWikiGuest**</code>. You can enable this by setting the <code>**$doRememberRemoteUser**</code> flag in <code>**TWiki.cfg**</code>. TWiki persistently stores the IP address / username pairs in file <code>**$remoteUserFilename**</code>, which is <code>**"$dataDir/remoteusers.txt"**</code> by default. Please note that this can fail if the IP address changes due to dynamically assigned IP addresses or proxy servers.
+There is a way to tell TWiki to remember the user for the scripts that are not authenticated, ex: in case the <code>**REMOTE\_USER**</code> environment variable is not set. TWiki can be configured to remember the IP address/username pair whenever an authentication happens (edit topic, attach file). Once remembered, the non-authenticated scripts like <code>**view**</code> will show the correct username instead of <code>**TWikiGuest**</code>. You can enable this by setting the <code>**$doRememberRemoteUser**</code> flag in <code>**TWiki.cfg**</code>. TWiki persistently stores the IP address/username pairs in the file <code>**$remoteUserFilename**</code>, which is <code>**"$dataDir/remoteusers.txt"**</code> by default. Please note that this can fail if the IP address changes due to dynamically assigned IP addresses or proxy servers.
 
 **Authentication Test:** You are Main.admin (%WIKIUSERNAME%)
 
@@ -42,7 +47,7 @@ This section applies only if your %WIKITOOLNAME% is installed on a server that i
 
 %WIKITOOLNAME% can automatically map an intranet username to a TWiki username, provided that the username pair exists in the [[TWikiUsers]] topic. This is also handled automatically when you register.
 
-> **_NOTE:_**
+> **NOTE:**
 >
 > **To correctly enter a [[WikiName]]**
 >
-- 
1.9.4