TWiki.TWikiUserAuthentication (r1.1 vs. r1.18)
Diffs

 <<O>>  Difference Topic TWikiUserAuthentication (r1.18 - 25 Apr 2004 - PeterThoeny)
Changed:
<
<
META TOPICINFO PeterThoeny date="1054178925" format="1.0" version="1.17"
>
>
META TOPICINFO PeterThoeny date="1082877324" format="1.0" version="1.18"

TWiki User Authentication

Line: 50 to 50

TWiki can automatically map an Intranet (Login) Username to a TWiki Username, provided that the username pair exists in the TWikiUsers topic. This is also handled automatically when you register.

Changed:
<
<
  • ALERT! In the original TWiki distribution, in twiki/data, there are two registration form topics, TWikiRegistration and TWikiRegistrationPub. The original form includes an intranet Login Username field. For Basic Authentication, the original form is replaced by the Pub version. If you started using TWiki on Basic Authentication and want to change, you have to switch back forms for future use, and manually correct the existing entries, by editing TWikiUsers, adding the Login Username for each member - PeterThoeny - pthoeny - 01 Jan 1999 - and also in the .htpasswd file, where you can either replace the WikiNames or duplicate the entries and have both, so both usernames will work. verification and clearer rewrite to follow in a bit. also link to original installation mention.
>
>
  • ALERT! In the original TWiki distribution, in twiki/data, there are two registration form topics, TWikiRegistration and TWikiRegistrationPub. The original form includes an intranet Login Username field. For Basic Authentication, the original form is replaced by the Pub version. If you started using TWiki on Basic Authentication and want to change, you have to switch back forms for future use, and manually correct the existing entries, by editing TWikiUsers, adding the Login Username for each member - PeterThoeny - pthoeny - 01 Jan 1999 - and also in the .htpasswd file, where you can either replace the WikiNames or duplicate the entries and have both, so both usernames will work.

NOTE: To correctly enter a WikiName - your own or someone else's - be sure to include the Main web name in front of the Wiki username, followed by a period, and no spaces. Ex:
Line: 75 to 75

Please only use this ResetPassword form in case you really forgot your password. Otherwise just change it using ChangePassword. Thank you.

Your WikiName: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form you will see a page with your new password appearing encrypted.

You will have to e-mail this information to the Wiki webmaster, rumcajs_78@users.sourceforgeNOSPAM.net, who will set your account to use the new password.

Changed:
<
<
-- MikeMannix? - 19 May 2002
>
>
-- TWiki.Main.MikeMannix - 19 May 2002
-- TWiki.Main.PeterThoeny - 25 Apr 2004


 <<O>>  Difference Topic TWikiUserAuthentication (r1.17 - 29 May 2003 - PeterThoeny)
Changed:
<
<
META TOPICINFO PeterThoeny date="1050303329" format="1.0" version="1.16"
>
>
META TOPICINFO PeterThoeny date="1054178925" format="1.0" version="1.17"

TWiki User Authentication

Line: 28 to 28

Tracking by IP address is an experimental feature, enabled in lib/TWiki.cfg. It lets you combine open access to some functions, with authentication on others, with full user activity tracking:

  • Normally, the REMOTE_USER environment variable is set for the scripts that are under authentication. If, for example, the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest instead of your WikiName.
Deleted:
<
<

  • 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 view, will show the correct username instead of TWikiGuest.
Deleted:
<
<

  • Enable this feature by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki then persistently stores the IP address/username pairs in the file, $remoteUserFilename, which is "$dataDir/remoteusers.txt" by default.
Changed:
<
<
>
>
  • Copy the view script to viewauth (or better, create a symbolic link)
  • Add viewauth to the list of authenticated scripts in the twiki/bin/.htaccess file. The view script should not be listed in the .htaccess file.

  • ALERT! This approach can fail if the IP address changes due to dynamically assigned IP addresses or proxy servers.

Quick Authentication Test - Use the %WIKIUSERNAME% variable to return your current identity:


 <<O>>  Difference Topic TWikiUserAuthentication (r1.16 - 14 Apr 2003 - PeterThoeny)
Changed:
<
<
META TOPICINFO PeterThoeny date="1041127470" format="1.0" version="1.15"
>
>
META TOPICINFO PeterThoeny date="1050303329" format="1.0" version="1.16"

TWiki User Authentication

Line: 11 to 11

Authentication Options

Changed:
<
<
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 TWikiGuest default identity, so you can't track individual user activity.
  2. Use SSL (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server.
  3. Use Basic Authentication (.htaccess) to control access by protecting key scripts: attach, edit=, installpasswd, preview, rename, save, upload using the .htaccess file. The TWikiInstallationGuide has step-by-step instructions.
>
>
No special installation steps are required if the server is already authenticated. If it isn't, you have these options for controlling user access:
  1. No login at all: Forget about authentication to make your site completely public - anyone can browse and edit freely, in classic Wiki mode. All visitors are assigned the TWikiGuest default identity, so you can't track individual user activity.
    • How: Default, no web server configuration necessary
  2. No login to view; require login to edit: Keeping track of who changed what and when, while keeping view access unrestricted is desirable in most TWiki deployments. This option is not suitable if you need TWikiAccessControl for view restricted content since TWiki does not know who a user is when looking at content.
    • How: Use Basic Authentication (.htaccess) to control access by protecting key scripts: attach, edit, installpasswd, manage, preview, rename, save, upload using the .htaccess file. The TWikiInstallationGuide has step-by-step instructions.
  3. No login to view unless necessary; require login to edit: You prefer not to bother the user with login for unrestricted content, but you need TWikiAccessControl for view restricted content. There are two ways to accomplish this:
    • How 1: Use Basic Authentication with Partial Authentication (described below)
    • How 2: Use one of the Session TWiki:Plugins where you give the user the option to login and logout.
  4. Require login to view and edit: Most restrictive, but TWiki knows who the user is at all times. There are two ways to accomplish this:
    • How 1: Use Basic Authentication to authenticate the whole twiki/bin directory. Consult your web server documentation.
    • How 1: Use SSL (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server. Consult your web server documentation.

Partial Authentication


 <<O>>  Difference Topic TWikiUserAuthentication (r1.15 - 29 Dec 2002 - PeterThoeny)
Changed:
<
<
META TOPICINFO MikeMannix? date="1021820542" format="1.0" version="1.14"
>
>
META TOPICINFO PeterThoeny date="1041127470" format="1.0" version="1.15"

TWiki User Authentication

Line: 44 to 44

TWiki can automatically map an Intranet (Login) Username to a TWiki Username, provided that the username pair exists in the TWikiUsers topic. This is also handled automatically when you register.

Changed:
<
<
  • ALERT! In the original TWiki distribution, in twiki/data, there are two registration form topics, TWikiRegistration and TWikiRegistrationPub. The original form includes an intranet Login Username field. For Basic Authentication, the original form is replaced by the Pub version. If you started using TWiki on Basic Authentication and want to change, you have to switch back forms for future use, and manually correct the existing entries, by editing TWikiUsers?, adding the Login Username for each member - PeterThoeny - pthoeny - 01 Jan 1999 - and also in the .htpasswd file, where you can either replace the WikiNames or duplicate the entries and have both, so both usernames will work. verification and clearer rewrite to follow in a bit. also link to original installation mention.
>
>
  • ALERT! In the original TWiki distribution, in twiki/data, there are two registration form topics, TWikiRegistration and TWikiRegistrationPub. The original form includes an intranet Login Username field. For Basic Authentication, the original form is replaced by the Pub version. If you started using TWiki on Basic Authentication and want to change, you have to switch back forms for future use, and manually correct the existing entries, by editing TWikiUsers, adding the Login Username for each member - PeterThoeny - pthoeny - 01 Jan 1999 - and also in the .htpasswd file, where you can either replace the WikiNames or duplicate the entries and have both, so both usernames will work. verification and clearer rewrite to follow in a bit. also link to original installation mention.

NOTE: To correctly enter a WikiName - your own or someone else's - be sure to include the Main web name in front of the Wiki username, followed by a period, and no spaces. Ex:

 <<O>>  Difference Topic TWikiUserAuthentication (r1.14 - 19 May 2002 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="1000545481" format="1.0" version="1.13"
>
>
META TOPICINFO MikeMannix? date="1021820542" format="1.0" version="1.14"

TWiki User Authentication

Changed:
<
<
TWiki site access control and user activity tracking

Overview

>
>
TWiki site access control and user activity tracking options

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).

Line: 14 to 12

Authentication Options

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:

Changed:
<
<
  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 TWikiGuest default identity, so you can't track individual user activity.
  2. Use SSL (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server.
  3. Use Basic Authentication (.htaccess) to control access by protecting key scripts: attach, edit=, installpasswd, preview, rename, save, upload using the .htaccess file. The TWikiInstallationGuide has step-by-step instructions.
>
>
  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 TWikiGuest default identity, so you can't track individual user activity.
  2. Use SSL (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server.
  3. Use Basic Authentication (.htaccess) to control access by protecting key scripts: attach, edit=, installpasswd, preview, rename, save, upload using the .htaccess file. The TWikiInstallationGuide has step-by-step instructions.

Partial Authentication

Line: 28 to 26

  • Enable this feature by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki then persistently stores the IP address/username pairs in the file, $remoteUserFilename, which is "$dataDir/remoteusers.txt" by default.
Changed:
<
<
  • NOTE: This approach can fail if the IP address changes due to dynamically assigned IP addresses or proxy servers.
>
>
  • ALERT! This approach can fail if the IP address changes due to dynamically assigned IP addresses or proxy servers.

Quick Authentication Test - Use the %WIKIUSERNAME% variable to return your current identity:

Line: 36 to 34

TWiki Username vs. Login Username

Changed:
<
<
This section applies only if your JCuckoo is installed on a server that is both authenticated and on an intranet.
>
>
This section applies only if your TWiki site is installed on a server that is both authenticated and on an intranet.

JCuckoo internally manages two usernames: Login Username and TWiki Username.


Changed:
<
<
JCuckoo internally manages two usernames: Login username and TWiki username.
>
>
  • Login Username: When you login to the intranet, you use your existing login username, ex: pthoeny. This name is normally passed to TWiki by the REMOTE_USER environment variable, and used internally. Login Usernames are maintained by your system administrator.

Changed:
<
<
  • Login username: When you login to the intranet, you use your existing login username, ex: pthoeny. This name is normally passed to JCuckoo by the REMOTE_USER environment variable, and used by internally by JCuckoo. Login usernames are maintained by your system administrator.
>
>
  • TWiki Username: Your name in WikiNotation, ex: PeterThoeny, is recorded when you register using TWikiRegistration; doing so also generates a personal home page in the Main web.

Changed:
<
<
  • TWiki username: Your name in WikiNotation, ex: PeterThoeny, is recorded when you register using TWikiRegistration; doing so also generates a personal home page in the Main web.
>
>
TWiki can automatically map an Intranet (Login) Username to a TWiki Username, provided that the username pair exists in the TWikiUsers topic. This is also handled automatically when you register.

Changed:
<
<
JCuckoo 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.
>
>
  • ALERT! In the original TWiki distribution, in twiki/data, there are two registration form topics, TWikiRegistration and TWikiRegistrationPub. The original form includes an intranet Login Username field. For Basic Authentication, the original form is replaced by the Pub version. If you started using TWiki on Basic Authentication and want to change, you have to switch back forms for future use, and manually correct the existing entries, by editing TWikiUsers?, adding the Login Username for each member - PeterThoeny - pthoeny - 01 Jan 1999 - and also in the .htpasswd file, where you can either replace the WikiNames or duplicate the entries and have both, so both usernames will work. verification and clearer rewrite to follow in a bit. also link to original installation mention.

NOTE: To correctly enter a WikiName - your own or someone else's - be sure to include the Main web name in front of the Wiki username, followed by a period, and no spaces. Ex:
Line: 69 to 69

Please only use this ResetPassword form in case you really forgot your password. Otherwise just change it using ChangePassword. Thank you.

Your WikiName: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form you will see a page with your new password appearing encrypted.

You will have to e-mail this information to the Wiki webmaster, rumcajs_78@users.sourceforgeNOSPAM.net, who will set your account to use the new password.

Added:
>
>
-- MikeMannix? - 19 May 2002


Deleted:
<
<
-- MikeMannix? - 29 Aug 2001

META TOPICMOVED MikeMannix? date="999320061" from="TWiki.TWikiAuthentication" to="TWiki.TWikiUserAuthentication"

 <<O>>  Difference Topic TWikiUserAuthentication (r1.13 - 15 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO PeterThoeny date="1000454534" format="1.0" version="1.12"
Note: Included topic UtilTempDocNote? does not exist yet
>
>
META TOPICINFO MikeMannix? date="1000545481" format="1.0" version="1.13"

TWiki User Authentication

Line: 9 to 7

Overview

Changed:
<
<
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 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.

Authentication Options

Changed:
<
<
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 TWikiGuest default identity, so you can't track individual user activity.
  2. Use SSL (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server.
  3. Use Basic Authentication (.htaccess) to control access by protecting key scripts: attach, edit=, installpasswd, preview, rename, save, upload using the .htaccess file. The TWikiInstallationGuide has step-by-step instructions.
Line: 61 to 59

Changed:
<
<
>
>

Forgot your old password? Then use ResetPassword instead. Please only use ResetPassword in case you really forgot your password. Thank you.

Your WikiName: **
Old password: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form your password will be changed.

If you have questions please contact the TWiki webmaster rumcajs_78@users.sourceforgeNOSPAM.net.

Changed:
<
<
>
>

Please only use this ResetPassword form in case you really forgot your password. Otherwise just change it using ChangePassword. Thank you.

Your WikiName: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form you will see a page with your new password appearing encrypted.

You will have to e-mail this information to the Wiki webmaster, rumcajs_78@users.sourceforgeNOSPAM.net, who will set your account to use the new password.


 <<O>>  Difference Topic TWikiUserAuthentication (r1.12 - 14 Sep 2001 - PeterThoeny)
Changed:
<
<
META TOPICINFO MikeMannix? date="1000280080" format="1.0" version="1.11"
>
>
META TOPICINFO PeterThoeny date="1000454534" format="1.0" version="1.12"

Note: Included topic UtilTempDocNote? does not exist yet

TOC: No TOC in "TWiki.TWikiUserAuthentication"

Line: 18 to 18

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:
  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 TWikiGuest default identity, so you can't track individual user activity.
  2. Use SSL (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server.
Changed:
<
<
  1. Use Basic Authentication (HTAccess) to control access by protecting key scripts: attach, edit=, installpasswd, password, preview, rename, save, upload, view, viewfile using .htaccess files. The TWiki Installation Guide has step-by-step instructions.
>
>
  1. Use Basic Authentication (.htaccess) to control access by protecting key scripts: attach, edit=, installpasswd, preview, rename, save, upload using the .htaccess file. The TWikiInstallationGuide has step-by-step instructions.

Partial Authentication


 <<O>>  Difference Topic TWikiUserAuthentication (r1.11 - 12 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="999857118" format="1.0" version="1.10"
>
>
META TOPICINFO MikeMannix? date="1000280080" format="1.0" version="1.11"
Note: Included topic UtilTempDocNote? does not exist yet

TWiki User Authentication


 <<O>>  Difference Topic TWikiUserAuthentication (r1.10 - 07 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="999811937" format="1.0" version="1.9"
>
>
META TOPICINFO MikeMannix? date="999857118" format="1.0" version="1.10"

TOC: No TOC in "TWiki.TWikiUserAuthentication"
Changed:
<
<

TWiki User Authentication

>
>

TWiki User Authentication


TWiki site access control and user activity tracking

Changed:
<
<

Overview

>
>

Overview


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.

Changed:
<
<

Authentication Options

>
>

Authentication Options


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:

  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 TWikiGuest default identity, so you can't track individual user activity.
  2. Use SSL (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server.
  3. Use Basic Authentication (HTAccess) to control access by protecting key scripts: attach, edit=, installpasswd, password, preview, rename, save, upload, view, viewfile using .htaccess files. The TWiki Installation Guide has step-by-step instructions.
Changed:
<
<

Partial Authentication

>
>

Partial Authentication


Tracking by IP address is an experimental feature, enabled in lib/TWiki.cfg. It lets you combine open access to some functions, with authentication on others, with full user activity tracking:

Line: 34 to 34

Changed:
<
<

TWiki Username vs. Login Username

>
>

TWiki Username vs. Login Username


This section applies only if your JCuckoo is installed on a server that is both authenticated and on an intranet.

Line: 53 to 53

Changed:
<
<

Changing Passwords

>
>

Changing Passwords


Change and reset passwords using forms on regular pages. Use TWikiAccessControl to restrict use as required.

Line: 70 to 70

Deleted:
<
<
-- PeterThoeny - 16 Mar 2001

-- MikeMannix? - 29 Aug 2001
Deleted:
<
<

META TOPICMOVED MikeMannix? date="999320061" from="TWiki.TWikiAuthentication" to="TWiki.TWikiUserAuthentication"

 <<O>>  Difference Topic TWikiUserAuthentication (r1.9 - 06 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="999755787" format="1.0" version="1.8"
>
>
META TOPICINFO MikeMannix? date="999811937" format="1.0" version="1.9"

TWiki User Authentication

Line: 13 to 13

Authentication Options

Changed:
<
<
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 - anyone can browse and edit freely, in classic Wiki mode.
  2. Use Basic Authentication for the edit and attach scripts. This uses .htaccess and generates the familiar grey log-in window. The TWiki Installation Guide has step-by-step instructions.
  3. Use SSL to authenticate and secure the whole server.
>
>
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:
  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 TWikiGuest default identity, so you can't track individual user activity.
  2. Use SSL (Secure Sockets Layer; HTTPS) to authenticate and secure the whole server.
  3. Use Basic Authentication (HTAccess) to control access by protecting key scripts: attach, edit=, installpasswd, password, preview, rename, save, upload, view, viewfile using .htaccess files. The TWiki Installation Guide has step-by-step instructions.

Changed:
<
<

Tracking by IP Address

>
>

Partial Authentication


Changed:
<
<
The REMOTE_USER environment variable is only set for the scripts that are under authentication. If, for example, the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest instead of your WikiName.
>
>
Tracking by IP address is an experimental feature, enabled in lib/TWiki.cfg. It lets you combine open access to some functions, with authentication on others, with full user activity tracking:

Changed:
<
<
There is a way to tell TWiki to remember the user for the scripts that are not authenticated, ex: in case the REMOTE_USER 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 view will show the correct username instead of TWikiGuest. You can enable this by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki persistently stores the IP address/username pairs in the file $remoteUserFilename, which is "$dataDir/remoteusers.txt" by default. Please note that this can fail if the IP address changes due to dynamically assigned IP addresses or proxy servers.
>
>
  • Normally, the REMOTE_USER environment variable is set for the scripts that are under authentication. If, for example, the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest instead of your WikiName.

Changed:
<
<
Authentication Test: You are TWikiGuest (%WIKIUSERNAME%)
>
>
  • 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 view, will show the correct username instead of TWikiGuest.

  • Enable this feature by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki then persistently stores the IP address/username pairs in the file, $remoteUserFilename, which is "$dataDir/remoteusers.txt" by default.

  • NOTE: This approach can fail if the IP address changes due to dynamically assigned IP addresses or proxy servers.

Quick Authentication Test - Use the %WIKIUSERNAME% variable to return your current identity:


TWiki Username vs. Login Username

Line: 38 to 47

JCuckoo 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.

Changed:
<
<
NOTE: *To correctly enter a WikiName* - your own or someone else's - be sure to include the Main web name in front of the Wiki username, followed by a period, and no spaces. Ex:
>
>
NOTE: To correctly enter a WikiName - your own or someone else's - be sure to include the Main web name in front of the Wiki username, followed by a period, and no spaces. Ex:

Main.WikiUsername or %MAINWEB%.WikiUsername
This points WikiUser to the JCuckoo.Main web, where user registration pages are stored, no matter which web it's entered in. Without the web prefix, the name appears as a NewTopic? everywhere but in the Main web.
Line: 46 to 55

Changing Passwords

Changed:
<
<
Change and reset passwords using forms on regular pages. Use topic-level TWikiAccessControl to restrict use as required.
>
>
Change and reset passwords using forms on regular pages. Use TWikiAccessControl to restrict use as required.

Changed:
<
<
>
>

Forgot your old password? Then use ResetPassword instead. Please only use ResetPassword in case you really forgot your password. Thank you.

Your WikiName: **
Old password: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form your password will be changed.

If you have questions please contact the TWiki webmaster rumcajs_78@users.sourceforgeNOSPAM.net.

Changed:
<
<
>
>

Please only use this ResetPassword form in case you really forgot your password. Otherwise just change it using ChangePassword. Thank you.

Your WikiName: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form you will see a page with your new password appearing encrypted.

You will have to e-mail this information to the Wiki webmaster, rumcajs_78@users.sourceforgeNOSPAM.net, who will set your account to use the new password.


 <<O>>  Difference Topic TWikiUserAuthentication (r1.8 - 06 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="999567701" format="1.0" version="1.7"
>
>
META TOPICINFO MikeMannix? date="999755787" format="1.0" version="1.8"

TWiki User Authentication

Changed:
<
<
Controlling TWiki site access and logging authorized user activity
>
>
TWiki site access control and user activity tracking

Overview

Line: 14 to 14

Authentication Options

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:

Changed:
<
<
  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.
  2. Use Basic Authentication for the edit and attach scripts. This uses .htaccess and generates the familiar grey log-in window. The TWiki Installation Guide has step-by-step instructions.
  3. Use SSL to authenticate and secure the whole server.
>
>
  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.
  2. Use Basic Authentication for the edit and attach scripts. This uses .htaccess and generates the familiar grey log-in window. The TWiki Installation Guide has step-by-step instructions.
  3. Use SSL to authenticate and secure the whole server.

Tracking by IP Address

Line: 43 to 43

This points WikiUser to the JCuckoo.Main web, where user registration pages are stored, no matter which web it's entered in. Without the web prefix, the name appears as a NewTopic? everywhere but in the Main web.
Added:
>
>

Changing Passwords

Added:
>
>
Change and reset passwords using forms on regular pages. Use topic-level TWikiAccessControl to restrict use as required.


Forgot your old password? Then use ResetPassword instead. Please only use ResetPassword in case you really forgot your password. Thank you.

Your WikiName: **
Old password: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form your password will be changed.

If you have questions please contact the TWiki webmaster rumcajs_78@users.sourceforgeNOSPAM.net.

Added:
>
>

Added:
>
>


Please only use this ResetPassword form in case you really forgot your password. Otherwise just change it using ChangePassword. Thank you.

Your WikiName: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form you will see a page with your new password appearing encrypted.

You will have to e-mail this information to the Wiki webmaster, rumcajs_78@users.sourceforgeNOSPAM.net, who will set your account to use the new password.

Added:
>
>

-- PeterThoeny - 16 Mar 2001
-- MikeMannix? - 29 Aug 2001


 <<O>>  Difference Topic TWikiUserAuthentication (r1.7 - 04 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="999502042" format="1.0" version="1.6"
>
>
META TOPICINFO MikeMannix? date="999567701" format="1.0" version="1.7"

TWiki User Authentication

Line: 45 to 45

Changing Passwords

Changed:
<
<
Note: Included topic ChangingPasswords? does not exist yet
>
>

Forgot your old password? Then use ResetPassword instead. Please only use ResetPassword in case you really forgot your password. Thank you.

Your WikiName: **
Old password: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form your password will be changed.

If you have questions please contact the TWiki webmaster rumcajs_78@users.sourceforgeNOSPAM.net.

Please only use this ResetPassword form in case you really forgot your password. Otherwise just change it using ChangePassword. Thank you.

Your WikiName: **
New password: **
Retype new password: **
     (Fields marked ** are required)

After submitting this form you will see a page with your new password appearing encrypted.

You will have to e-mail this information to the Wiki webmaster, rumcajs_78@users.sourceforgeNOSPAM.net, who will set your account to use the new password.


-- PeterThoeny - 16 Mar 2001
-- MikeMannix? - 29 Aug 2001


 <<O>>  Difference Topic TWikiUserAuthentication (r1.6 - 03 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="999408728" format="1.0" version="1.5"
>
>
META TOPICINFO MikeMannix? date="999502042" format="1.0" version="1.6"

TWiki User Authentication

Line: 43 to 43

This points WikiUser to the JCuckoo.Main web, where user registration pages are stored, no matter which web it's entered in. Without the web prefix, the name appears as a NewTopic? everywhere but in the Main web.
Added:
>
>

Changing Passwords

Note: Included topic ChangingPasswords? does not exist yet


-- PeterThoeny - 16 Mar 2001
-- MikeMannix? - 29 Aug 2001

 <<O>>  Difference Topic TWikiUserAuthentication (r1.5 - 02 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="999320253" format="1.0" version="1.4"
>
>
META TOPICINFO MikeMannix? date="999408728" format="1.0" version="1.5"

TWiki User Authentication

Changed:
<
<
TWiki does not authenticate users internally, it depends on the REMOTE_USER 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

Overview

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.

Authentication Options

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:

Changed:
<
<
  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 edit and attach scripts. This uses .htaccess and generates the familiar grey log-in window. 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.
  2. Use Basic Authentication for the edit and attach scripts. This uses .htaccess and generates the familiar grey log-in window. The TWiki Installation Guide has step-by-step instructions.

  1. Use SSL to authenticate and secure the whole server.

Tracking by IP Address

The REMOTE_USER environment variable is only set for the scripts that are under authentication. If, for example, the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest instead of your WikiName.

Changed:
<
<
There is a way to tell TWiki to remember the user for the scripts that are not authenticated, ex: in case the REMOTE_USER 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 view will show the correct username instead of TWikiGuest. You can enable this by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki persistently stores the IP address / username pairs in file $remoteUserFilename, which is "$dataDir/remoteusers.txt" 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 REMOTE_USER 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 view will show the correct username instead of TWikiGuest. You can enable this by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki persistently stores the IP address/username pairs in the file $remoteUserFilename, which is "$dataDir/remoteusers.txt" 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 TWikiGuest (%WIKIUSERNAME%)

Line: 34 to 38

JCuckoo 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.

Changed:
<
<
NOTE: To correctly enter a WikiName - your own or someone else's - be sure to include the Main web name in front of the Wiki username, followed by a period, and no spaces. Ex:
>
>
NOTE: *To correctly enter a WikiName* - your own or someone else's - be sure to include the Main web name in front of the Wiki username, followed by a period, and no spaces. Ex:

Main.WikiUsername or %MAINWEB%.WikiUsername
This points WikiUser to the JCuckoo.Main web, where user registration pages are stored, no matter which web it's entered in. Without the web prefix, the name appears as a NewTopic? everywhere but in the Main web.

 <<O>>  Difference Topic TWikiUserAuthentication (r1.4 - 01 Sep 2001 - MikeMannix?)
Changed:
<
<
META TOPICINFO MikeMannix? date="999098621" format="1.0" version="1.3"
>
>
META TOPICINFO MikeMannix? date="999320253" format="1.0" version="1.4"

TOC: No TOC in "TWiki.TWikiUserAuthentication"
Changed:
<
<

TWiki Authentication

>
>

TWiki User Authentication


TWiki does not authenticate users internally, it depends on the REMOTE_USER environment variable. This variable is set when you enable basic authentication or authentication via SSL (https protocol).

Line: 41 to 41

-- PeterThoeny - 16 Mar 2001
-- MikeMannix? - 29 Aug 2001

Added:
>
>

META TOPICMOVED MikeMannix? date="999320061" from="TWiki.TWikiAuthentication" to="TWiki.TWikiUserAuthentication"

 <<O>>  Difference Topic TWikiUserAuthentication (r1.3 - 29 Aug 2001 - MikeMannix?)
Added:
>
>
META TOPICINFO MikeMannix? date="999098621" format="1.0" version="1.3"
TOC: No TOC in "TWiki.TWikiUserAuthentication"

TWiki Authentication

Changed:
<
<
TWiki does not authenticate users internally, it depends on the REMOTE_USER environment variable. This variable is set when you enable basic authentication or authentication via SSL (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 or authentication via SSL (https protocol).

Changed:
<
<
TWiki keeps track who made changes to topics at what time. This gives a complete audit trail of changes.
>
>
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.

Changed:
<
<
No special installation steps need to be performed in case the server is already autenticated. If not you can opt for one of these:
  • Forget about authentication. All changes will be registered as TWikiGuest user, e.g. you can't tell who made changes.
  • Use basic authentication for the edit and attach scripts. TWiki Installation Notes tells you more about that.
  • Use SSL to authenticate and secure the whole server.
>
>

Authentication Options


Changed:
<
<
The REMOTE_USER environment variable is only set for the scripts that are under authentication. If for example the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest instead of your WikiName.
>
>
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 edit and attach scripts. This uses .htaccess and generates the familiar grey log-in window. TWiki Installation Notes has more.
  3. Use SSL to authenticate and secure the whole server.

Changed:
<
<
There is a way to tell TWiki to remember the user for the scripts that are not authenticated, e.g. for the case where the REMOTE_USER 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 view will show the correct username instead of TWikiGuest. You can enable this by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki persistently stores the IP address / username pairs in file $remoteUserFilename, which is "$dataDir/remoteusers.txt" by default. Please note that this can fail in case the IP address changes due to dynamically assigned IP addresses or proxy servers.
>
>

Tracking by IP Address


Changed:
<
<
Test: You are TWikiGuest.
>
>
The REMOTE_USER environment variable is only set for the scripts that are under authentication. If, for example, the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest 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 REMOTE_USER 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 view will show the correct username instead of TWikiGuest. You can enable this by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki persistently stores the IP address / username pairs in file $remoteUserFilename, which is "$dataDir/remoteusers.txt" 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 TWikiGuest (%WIKIUSERNAME%)

TWiki Username vs. Login Username

This section applies only if your JCuckoo is installed on a server that is both authenticated and on an intranet.

JCuckoo internally manages two usernames: Login username and TWiki username.

  • Login username: When you login to the intranet, you use your existing login username, ex: pthoeny. This name is normally passed to JCuckoo by the REMOTE_USER environment variable, and used by internally by JCuckoo. Login usernames are maintained by your system administrator.
  • TWiki username: Your name in WikiNotation, ex: PeterThoeny, is recorded when you register using TWikiRegistration; doing so also generates a personal home page in the Main web.

JCuckoo 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: To correctly enter a WikiName - your own or someone else's - be sure to include the Main web name in front of the Wiki username, followed by a period, and no spaces. Ex:
Main.WikiUsername or %MAINWEB%.WikiUsername
This points WikiUser to the JCuckoo.Main web, where user registration pages are stored, no matter which web it's entered in. Without the web prefix, the name appears as a NewTopic? everywhere but in the Main web.

-- PeterThoeny - 16 Mar 2001

Added:
>
>
-- MikeMannix? - 29 Aug 2001

 <<O>>  Difference Topic TWikiUserAuthentication (r1.2 - 16 Mar 2001 - PeterThoeny)
Changed:
<
<
TWiki does not authenticate users internally, it depends on the REMOTE_USER environment variable. This variable is set when you enable basic authentication or authentication via SSL (https protocol)
>
>

TWiki Authentication

TWiki does not authenticate users internally, it depends on the REMOTE_USER environment variable. This variable is set when you enable basic authentication or authentication via SSL (https protocol)


TWiki keeps track who made changes to topics at what time. This gives a complete audit trail of changes.

No special installation steps need to be performed in case the server is already autenticated. If not you can opt for one of these:

  • Forget about authentication. All changes will be registered as TWikiGuest user, e.g. you can't tell who made changes.
Changed:
<
<
  • Use basic authentication for the edit and attach scripts. TWiki Installation tells you more about that.
>
>

  • Use SSL to authenticate and secure the whole server.
Changed:
<
<
The REMOTE_USER environment variable is only set for the scripts that are under authentication. If for example the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest instead of your WikiName.
>
>
The REMOTE_USER environment variable is only set for the scripts that are under authentication. If for example the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest instead of your WikiName.

There is a way to tell TWiki to remember the user for the scripts that are not authenticated, e.g. for the case where the REMOTE_USER 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 view will show the correct username instead of TWikiGuest. You can enable this by setting the $doRememberRemoteUser flag in TWiki.cfg. TWiki persistently stores the IP address / username pairs in file $remoteUserFilename, which is "$dataDir/remoteusers.txt" by default. Please note that this can fail in case the IP address changes due to dynamically assigned IP addresses or proxy servers.


Changed:
<
<
There is a way to tell TWiki to remember the user for the scripts that are not authenticated, e.g. for the case where the REMOTE_USER 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 view will show the correct username instead of TWikiGuest. You can enable this by setting the $doRememberRemoteUser flag in wikicfg.pm. TWiki persistently stores the IP address / username pairs in file $remoteUserFilename, which is "$dataDir/remoteusers.txt" by default. Please note that this can fail in case the IP address changes due to dynamically assigned IP addresses or proxy servers. Test: You are TWikiGuest.
>
>
Test: You are TWikiGuest.

Changed:
<
<
-- PeterThoeny - 02 Nov 2000
>
>
-- PeterThoeny - 16 Mar 2001

 <<O>>  Difference Topic TWikiUserAuthentication (r1.1 - 02 Nov 2000 - PeterThoeny)
Line: 1 to 1
Added:
>
>
TWiki does not authenticate users internally, it depends on the REMOTE_USER environment variable. This variable is set when you enable basic authentication or authentication via SSL (https protocol)

TWiki keeps track who made changes to topics at what time. This gives a complete audit trail of changes.

No special installation steps need to be performed in case the server is already autenticated. If not you can opt for one of these:

  • Forget about authentication. All changes will be registered as TWikiGuest user, e.g. you can't tell who made changes.
  • Use basic authentication for the edit and attach scripts. TWiki Installation tells you more about that.
  • Use SSL to authenticate and secure the whole server.

The REMOTE_USER environment variable is only set for the scripts that are under authentication. If for example the edit, save and preview scripts are authenticated, but not view, you would get your WikiName in preview for the %WIKIUSERNAME% variable, but view will show TWikiGuest instead of your WikiName.

There is a way to tell TWiki to remember the user for the scripts that are not authenticated, e.g. for the case where the REMOTE_USER 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 view will show the correct username instead of TWikiGuest. You can enable this by setting the $doRememberRemoteUser flag in wikicfg.pm. TWiki persistently stores the IP address / username pairs in file $remoteUserFilename, which is "$dataDir/remoteusers.txt" by default. Please note that this can fail in case the IP address changes due to dynamically assigned IP addresses or proxy servers. Test: You are TWikiGuest.

-- PeterThoeny - 02 Nov 2000


Topic: TWikiUserAuthentication . { View | Diffs | r1.18 | > | r1.17 | > | r1.16 | More }

Revision r1.1 - 02 Nov 2000 - 09:23 - PeterThoeny
Revision r1.18 - 25 Apr 2004 - 07:15 - PeterThoeny