diff options
| -rw-r--r-- | TWiki/TWikiUserAuthentication.mdwn | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/TWiki/TWikiUserAuthentication.mdwn b/TWiki/TWikiUserAuthentication.mdwn index 7314e925..c62170a8 100644 --- a/TWiki/TWikiUserAuthentication.mdwn +++ b/TWiki/TWikiUserAuthentication.mdwn @@ -1,5 +1,3 @@ -%INCLUDE\{"UtilTempDocNote"\}% - %TOC% %STARTINCLUDE% # <a name="TWiki_User_Authentication"> TWiki User Authentication </a> @@ -8,13 +6,13 @@ _TWiki site access control and user activity tracking_ ## <a name="Overview"> Overview </a> -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 does not authenticate users internally, it depends on the `REMOTE_USER` 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. ## <a name="Authentication_Options"> Authentication Options </a> -No special installation steps need to be performed if the server is already authenticated. If not, you have three standard options for controlling user access: +No special installation steps are required if the server is already authenticated. If it isn't, you have three standard options for controlling user access: 1. **Forget about authentication** to make your site completely public - anyone can browse and edit freely, in classic Wiki mode. All visitors are assigned the %MAINWEB%.TWikiGuest default identity, so you can't track individual user activity. <br /> 2. **Use SSL** (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server. <br /> |