Item109: TWikiUserAuthentication -> UserAuthentication

git-svn-id: http://svn.foswiki.org/trunk@518 0b4bb1d4-4e5a-0410-9cc4-b2b747904278

core/data/TWiki/TWikiAccessControl.txt

@@ -4,7 +4,7 @@
 
 _Restricting read and write access to topics and webs, by Users and groups_
 
-TWiki Access Control allows you restrict access to single topics and entire webs, by individual user and by user Groups. Access control, combined with TWikiUserAuthentication, lets you easily create and manage an extremely flexible, fine-grained privilege system.
+TWiki Access Control allows you restrict access to single topics and entire webs, by individual user and by user Groups. Access control, combined with UserAuthentication, lets you easily create and manage an extremely flexible, fine-grained privilege system.
 
 __%T% Tip:__ TWiki:TWiki.TWikiAccessControlSupplement on TWiki.org has additional documentation on access control.
 
@@ -30,7 +30,7 @@ __Note:__ Above table comes from SitePermissions
 
 ---++ Authentication vs. Access Control
 
-*Authentication:* Identifies who a user is based on a login procedure. See TWikiUserAuthentication.
+*Authentication:* Identifies who a user is based on a login procedure. See UserAuthentication.
 
 *Access control:* Restrict access to content based on users and groups once a user is identified.
 
@@ -205,7 +205,7 @@ __%X% Note:__ Obfuscating a web without view access control is *very* insecure,
 
 ---+++ Restrict Access to Whole TWiki Site
 
-For a firewalled TWiki, e.g. an intranet wiki or extranet wiki, you want to allow only invited people to access your TWiki. In this case, enable [[TWikiUserAuthentication#ApacheLogin][user authentication with ApacheLogin]] and lock down access to the whole =twiki/bin= and =twiki/pub= directories to all but valid users. In the Apache =.htaccess= file or the appropriate =.conf= file, replace the =<FilesMatch "(attach|edit|...= section with this:
+For a firewalled TWiki, e.g. an intranet wiki or extranet wiki, you want to allow only invited people to access your TWiki. In this case, enable [[UserAuthentication#ApacheLogin][user authentication with ApacheLogin]] and lock down access to the whole =twiki/bin= and =twiki/pub= directories to all but valid users. In the Apache =.htaccess= file or the appropriate =.conf= file, replace the =<FilesMatch "(attach|edit|...= section with this:
 
 <verbatim>
 <FilesMatch ".*">
@@ -219,7 +219,7 @@ __Note:__ With this configuration, someone with access to the site needs to regi
 
 ---+++ Authenticate all Webs and Restrict Selected Webs
 
-Use the following setup to authenticate users for topic viewing in all webs and to restrict access to selected webs. Requires TWikiUserAuthentication to be enabled.
+Use the following setup to authenticate users for topic viewing in all webs and to restrict access to selected webs. Requires UserAuthentication to be enabled.
 
    1. Set =require valid-user= on your =view= script in .htaccess or the appropriate Apache .conf file. As of 4.x, this looks like: =FilesMatch "(attach|edit|manage|rename|save|view|upload|mail|logon|.*auth).*"= (normally =view= is not in that list).
    1. *Restrict* view access to selected Users and Groups. Set one or both of these variables in its %WEBPREFSTOPIC% topic:
@@ -230,7 +230,7 @@ Use the following setup to authenticate users for topic viewing in all webs and
 
 ---+++ Authenticate and Restrict Selected Webs Only
 
-Use the following setup to provide unrestricted viewing access to open webs, with authentication only on selected webs. Requires TWikiUserAuthentication to be enabled.
+Use the following setup to provide unrestricted viewing access to open webs, with authentication only on selected webs. Requires UserAuthentication to be enabled.
 
    1. *Restrict* view access to selected Users and Groups. Set one or both of these variables in its %WEBPREFSTOPIC% topic:
       * ==Set <nop>DENYWEBVIEW = &lt; list of Users and Groups &gt;==
@@ -251,5 +251,5 @@ Alternatively, place them in HTML comment markers, but this exposes the access s
 
 %STOPINCLUDE%
 
-__Related Topics:__ AdminDocumentationCategory, TWikiUserAuthentication, TWiki:TWiki.TWikiAccessControlSupplement
+__Related Topics:__ AdminDocumentationCategory, UserAuthentication, TWiki:TWiki.TWikiAccessControlSupplement
 

core/data/TWiki/TWikiDocumentation.txt

@@ -23,7 +23,7 @@ __Related Topics:__ TWikiSite, TWikiHistory, TWikiPlannedFeatures, TWikiEnhancem
 [[#PageTop][Back to top]]
 
 ------
-%INCLUDE{"TWikiUserAuthentication"}%
+%INCLUDE{"UserAuthentication"}%
 
 [[#PageTop][Back to top]]
 

core/data/TWiki/TWikiInstallationGuide.txt

@@ -88,7 +88,7 @@ Once you have TWiki installed and running, you might consider the following opti
 #AuthenticationOfUsers
 ---++ Enable Authentication of Users
 
-This step provides for site access control and user activity tracking on your TWiki site. __This is particularly important for sites that are publicly accessible on the web.__ This guide describes only the most common of several possible authentication setups for TWiki and is suitable for public web sites. For information about other setups, see =%SYSTEMWEB%.TWikiUserAuthentication=, and TWiki:TWiki.TWikiUserAuthenticationSupplement.
+This step provides for site access control and user activity tracking on your TWiki site. __This is particularly important for sites that are publicly accessible on the web.__ This guide describes only the most common of several possible authentication setups for TWiki and is suitable for public web sites. For information about other setups, see =%SYSTEMWEB%.UserAuthentication=, and TWiki:TWiki.UserAuthenticationSupplement.
 
 These are the steps for enabling "Template Login" which asks for a username and password in a web page, and processes them using the Apache 'htpasswd' password manager. Users can log in and log out.
 
@@ -100,7 +100,7 @@ These are the steps for enabling "Template Login" which asks for a username and
      %H% Check that the password manager recognizes the new user. Check that a new line with the username and encrypted password is added to the =data/.htpasswd= file. If not, you probably got a path wrong, or the permissions may not allow the webserver user to write to that file.
    1 Edit a topic (by clicking on the =Edit= link at beginning or end of topic) to check if authentication works.
 
-You are strongly encouraged to read =%SYSTEMWEB%.TWikiUserAuthentication=, TWiki:TWiki.TWikiUserAuthenticationSupplement, and TWiki:TWiki.SecuringTWikiSite for further information about managing users and security of your TWiki site.
+You are strongly encouraged to read =%SYSTEMWEB%.UserAuthentication=, TWiki:TWiki.UserAuthenticationSupplement, and TWiki:TWiki.SecuringTWikiSite for further information about managing users and security of your TWiki site.
 
 *Note!* The other =LoginManager= option =TWiki::LoginManager::ApacheLogin= uses a basic Apache type authentication where the browser itself prompts you for username and password. Most will find the !TemplateLogin looking nicer. But !ApacheLogin is required when you use Apache authentication methods like mod_ldap where all authentication is handled by an Apache module and not by the TWiki perl code. When you use !ApacheLogin the apache configuration must be set up to require authentication of the some but not all the scripts in the bin directory. This section in the Apache config (or .htaccess) controls this
 

core/data/TWiki/TWikiReferenceManual.txt

@@ -11,7 +11,7 @@ Manual sections in separate pages:
    1. [[TWikiSystemRequirements][TWiki System Requirements]]
    1. [[TWikiInstallationGuide][TWiki Installation Guide]]
    1. [[TWikiUpgradeGuide][TWiki Upgrade Guide]]
-   1. [[TWikiUserAuthentication][TWiki User Authentication]]
+   1. [[UserAuthentication][TWiki User Authentication]]
    1. [[TWikiAccessControl][TWiki Access Control]]
    1. [[TextFormattingRules][Text Formatting Rules]]
    1. [[TWikiVariables][TWiki Variables]]