(r1.1 vs. r1.29) TWikiAccessControl < TWiki

<<O>> Difference Topic TWikiAccessControl (r1.29 - 15 Aug 2004 - PeterThoeny)

Line: 205 to 205
	TOC: No TOC in "TWiki.TWikiAccessControl"
	The default setting is not to have superusers.
Changed:
< <	-- PeterThoeny - 04 May 2002 -- MikeMannix - 12 May 2002
> >	-- TWiki:Main.PeterThoeny - 04 May 2002 -- TWiki:Main.MikeMannix - 12 May 2002

Added:
> >

<<O>> Difference Topic TWikiAccessControl (r1.28 - 14 Apr 2003 - PeterThoeny)

Line: 25 to 25
	TOC: No TOC in "TWiki.TWikiAccessControl"
	Create broad-based Groups (for more and varied input), and... Avoid creating view-only Users (if you can read it, you should be able to contribute to it).
Added:
> >	Authentication vs. Access Control Authentication: Identifies who a user is based on a login procedure. See TWikiUserAuthentication. Access control: Restrict access to content based on users and groups once a user is identified.
	Users and Groups Access control is based on the familiar concept of Users and Groups. Users are defined by their WikiNames. They can then be organized in unlimited combinations by inclusion in one or more user Groups. For convenience, Groups can also be included in other Groups.

<<O>> Difference Topic TWikiAccessControl (r1.27 - 28 Dec 2002 - PeterThoeny)

Line: 31 to 31
	TOC: No TOC in "TWiki.TWikiAccessControl"
	Managing Users
Changed:
< <	A user is created with the TWikiRegistration form. The process generates a topic in the Main web in the new user's WikiName. The default visitor name is TWikiGuest.
> >	A user can create an account in TWikiRegistration. The following actions are performed:

Changed:
< <	Users can be authenticated using Basic Authentication (htaccess) or SSL (secure server). In either case, TWikiUserAuthentication is required in order to track user identities, and use User and Group access control.
> >	WikiName and encrypted password are recorded in `.htpasswd` if authentication is enabled. A confirmation e-mail is sent to the user. A user home page with the WikiName of the user is created in the Main web. The user is added to the TWikiUsers topic. Users can be authenticated using Basic Authentication (htaccess) or SSL (secure server). In either case, TWikiUserAuthentication is required in order to track user identities, and use User and Group access control. The default visitor name is TWikiGuest. This is the non-authenticated user.
	Managing Groups

<<O>> Difference Topic TWikiAccessControl (r1.26 - 29 May 2002 - PeterThoeny)

Line: 144 to 144
	TOC: No TOC in "TWiki.TWikiAccessControl"
	Restrict view access to selected Users and Groups. Set one or both of these variables in its WebPreferences topic: `Set DENYWEBVIEW = < list of Users and Groups >` `Set ALLOWWEBVIEW = < list of Users and Groups >`
Added:
> >	*Note:* `DENYWEBVIEW` is evaluated before `ALLOWWEBVIEW`. Access is denied if the authenticated person is in the `DENYWEBVIEW` list, or not in the `ALLOWWEBVIEW` list. Access is granted in case `DENYWEBVIEW` and `ALLOWWEBVIEW` is not defined.
	Hide the web from an "all webs" search. Enable this restriction with the `NOSEARCHALL` variable in its WebPreferences topic: `Set NOSEARCHALL = on` Add `view` to the list of authenticated scripts in the `.htaccess` file.
Line: 157 to 158
	Restrict view access to selected Users and Groups. Set one or both of these variables in its WebPreferences topic: `Set DENYWEBVIEW = < list of Users and Groups >` `Set ALLOWWEBVIEW = < list of Users and Groups >`
Added:
> >	*Note:* `DENYWEBVIEW` is evaluated before `ALLOWWEBVIEW`. Access is denied if the authenticated person is in the `DENYWEBVIEW` list, or not in the `ALLOWWEBVIEW` list. Access is granted in case `DENYWEBVIEW` and `ALLOWWEBVIEW` is not defined.
	Hide the web from an "all webs" search. Enable this restriction with the `NOSEARCHALL` variable in its WebPreferences topic: `Set NOSEARCHALL = on` Enable the `$doRememberRemoteUser` flag in `lib/TWiki.cfg` as described in TWikiUserAuthentication. GNHLUG will now remember the IP address of an authenticated user.
Line: 170 to 172
	Hiding Control Settings
Changed:
< <	To hide access control settings from normal browser viewing, place them in comment markers. <!-- Set DENYTOPICCHANGE = Main.SomeGroup -->
> >	To hide access control settings from normal browser viewing, place them in comment markers. `<!--` `* Set DENYTOPICCHANGE = Main.SomeGroup` `-->`
	The SuperAdminGroup

<<O>> Difference Topic TWikiAccessControl (r1.25 - 29 May 2002 - PeterThoeny)

 TOC: No TOC in "TWiki.TWikiAccessControl"
  DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in WebPreferences)

 ALLOWTOPICRENAME (in topic) overrides ALLOWWEBRENAME (in WebPreferences)
-<
<
+  Restricting Web Access
->
>
+  Restricting Read Access
-<
<
+You can prevent selected Users and Groups from accessing certain webs, by hiding them using restricting read access, or by requiring login. There are two basic methods, one simple, using standard preferences variables to hide a web, but offering low security, and a secure log-in approach that is currently a workaround, involving some minor script and filesystem modification.
->
>
+You can define who is allowed to see a web.
-<
<
+  Create Hidden Webs
->
>
+  Deny Viewing by Topic
-<
<
+You can prevent selected Users and Groups from viewing certain GNHLUG webs by setting one or both of these variables in each web's WebPreferences topic:
->
>
+ Technically it is possible to restrict read access to an individual topic based on DENYTOPICVIEW / ALLOWTOPICVIEW preferences variables, provided that the view script is authenticated. However this setup is not recommended since all content is searchable within a web - a search will turn up view restricted topics.

  Deny Viewing by Web 

You can define restrictions of who is allowed to view a GNHLUG web. You can restrict access to certain webs to selected Users and Groups, by:


 obfuscating webs: Insecure but handy method to hide new webs until content is ready for deployment.

 authenticating all webs and restricting selected webs: Topic access in all webs is authenticated, and selected webs have restricted access.

 authenticating and restricting selected webs only: Provide unrestricted viewing access to open webs, with authentication and restriction only on selected webs.



  Obfuscate Webs 

The idea is to keep a web hidden by not publishing its URL and by preventing the all webs search option from accessing obfuscated webs. Do so by enabling the NOSEARCHALL variable in WebPreferences:

 Set NOSEARCHALL = on



This setup can be useful to hide a new web until content its ready for deployment.

 Obfuscating webs is insecure, as anyone who knows the URL can access the web.

  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:


 Restrict view access to selected Users and Groups. Set one or both of these variables in its WebPreferences topic:
  Set DENYWEBVIEW = < list of Users and Groups >

 Set ALLOWWEBVIEW = < list of Users and Groups >
-<
<
+ If keeping a hidden web out of general use is a consideration, you can prevent the all webs search option from accessing hidden webs, by enabling the NOSEARCHALL variable in WebPreferences:
->
>
+ Hide the web from an "all webs" search. Enable this restriction with the NOSEARCHALL variable in its WebPreferences topic:
  Set NOSEARCHALL = on
-<
<
+ It is not recommended to restrict view access to individual topics since all content is searchable within a web.

 This method only works if the view script is authenticated, which means that all Users have to login, even for read-only access. (An open guest account, like TWikiGuest, can get around this, allowing anyone to login to a common account with, for example, view-only access for public webs.) TWikiInstallationGuide has more on Basic Authentication, using the .htaccess file.
->
>
+ Add view to the list of authenticated scripts in the .htaccess file.
-<
<
+ Hiding webs is not very secure, as there is a way to circumvent the read access restriction. It can be useful in certain situations - for example, to simplify site organization and clutter, by hiding low traffic webs - but is not recommended for securing sensitive content. (See the next section for a more secure approach.)
->
>
+ This method only works if the view script is authenticated, which means that all Users have to login, even for read-only access. (An open guest account, like TWikiGuest, can get around this, allowing anyone to login to a common account with, for example, view-only access for public webs.) TWikiInstallationGuide has more on Basic Authentication, using the .htaccess file.
-<
<
+  Create Authenticated Access By Web
->
>
+  Authenticate and Restricting Selected Webs Only
 Use the following setup to provide unrestricted viewing access to open webs, with authentication only on selected webs:
-<
<
+ Omit the view script from the .htaccess file.
->
>
+ Restrict view access to selected Users and Groups. Set one or both of these variables in its WebPreferences topic:

 Set DENYWEBVIEW = < list of Users and Groups >

 Set ALLOWWEBVIEW = < list of Users and Groups >



 Hide the web from an "all webs" search. Enable this restriction with the NOSEARCHALL variable in its WebPreferences topic:

 Set NOSEARCHALL = on
  Enable the $doRememberRemoteUser flag in lib/TWiki.cfg as described in TWikiUserAuthentication. GNHLUG will now remember the IP address of an authenticated user. 

 Copy the view script to viewauth (or better, create a symbolic link)
-<
<
+ Add viewauth to the list of authenticated scripts in the .htaccess file.
->
>
+ Add viewauth to the list of authenticated scripts in the .htaccess file. The view script should not be listed in the .htaccess file.



When a user accesses a web where you enabled view restriction, GNHLUG will redirect from the view script to the viewauth script once (this happens only if the user has never edited a topic). Doing so will ask for authentication. The viewauth script shows the requested topic if the user could log on and if the user is authorized to see that web.

 Authenticating webs is not very secure, as there is a way to circumvent the read access restriction. It can be useful in certain situations - for example, to simplify site organization and clutter, by hiding low traffic webs - but is not recommended for securing sensitive content.
-<
<
+ When a user accesses a web where you enabled view restriction, GNHLUG will redirect from the view script to the viewauth script once (this happens only if the user has never edited a topic). Doing so will ask for authentication. The viewauth script shows the requested topic if the user could log on and if the user is authorized to see that web.

 If you enable view restriction for a web, it is recommended to restrict search "all webs" from searching this web. Enable this restriction with the NOSEARCHALL variable in its WebPreferences, like:

 Set NOSEARCHALL = on



 It is not recommended to restrict view access to individual topics since all content is searchable within a web - a search will turn up the "hidden" topic.
   Hiding Control Settings

<<O>> Difference Topic TWikiAccessControl (r1.24 - 12 May 2002 - MikeMannix)

  TWiki Access Control





  TWiki Access Control
-<
<
+Restricting read and write access to topics and webs, by users and groups
->
>
+Restricting read and write access to topics and webs, by Users and groups
-<
<
+TWikiAccessControl allows you restrict access to single topics and entire webs, by individual user and by user groups, in three main areas: view; edit & attach; and rename/move/delete. These controls, combined with TWikiUserAuthentication, let you easily create and manage an extremely flexible, fine-grained privilege system.
->
>
+TWikiAccessControl allows you restrict access to single topics and entire webs, by individual user and by user Groups, in three areas: view; edit & attach; and rename/move/delete. Access control, combined with TWikiUserAuthentication, lets you easily create and manage an extremely flexible, fine-grained privilege system.
   An Important Control Consideration
-<
<
+Open, freeform editing is the essence of the WikiCulture - it's what makes TWiki different and often more effective than other collaboration tools. So, it is strongly recommended that decisions to restrict read or write access to a web or a topic are made with care. Experience shows that unrestricted write access works very well because:
->
>
+Open, freeform editing is the essence of WikiCulture - what makes TWiki different and often more effective than other collaboration tools. For that reason, it is strongly recommended that decisions to restrict read or write access to a web or a topic are made with care - the more restrictions, the less Wiki in the mix. Experience shows that unrestricted write access works very well because:
-<
<
+ Peer influence is enough to ensure that only relevant content is posted.
->
>
+ Peer influence is enough to ensure that only relevant content is posted.
-<
<
+ Peer editing - the ability to rearrange anything on a page - keeps topics focussed.
->
>
+ Peer editing - the ability for anyone to rearrange all content on a page - keeps topics focussed.
-<
<
+ All content is preserved under revision control.
->
>
+ In TWiki, content is transparently preserved under revision control:
  Edits can be undone by the TWikiAdminGroup (the default administrators group; see #ManagingGroups).

 Users are encouraged to edit and refactor (condense a long topic), since there's a safety net.
-<
<
+As a collaboration guideline:
->
>
+As a collaboration guideline:
-<
<
+ Create broad groups (more and varied input), and...

 Avoid creating view-only users (if you can read it, you can contribute to it).
->
>
+ Create broad-based Groups (for more and varied input), and...

 Avoid creating view-only Users (if you can read it, you should be able to contribute to it).
   Users and Groups
-<
<
+Access control is based on users and groups. Users are defined by their WikiNames, an then organized in unlimited combinations under different user groups.
->
>
+Access control is based on the familiar concept of Users and Groups. Users are defined by their WikiNames. They can then be organized in unlimited combinations by inclusion in one or more user Groups. For convenience, Groups can also be included in other Groups.
   Managing Users
-<
<
+A user is created by with the TWikiRegistration form. The process generates a topic in the Main web in the new user's WikiName. The default visitor name is TWikiGuest.
->
>
+A user is created with the TWikiRegistration form. The process generates a topic in the Main web in the new user's WikiName. The default visitor name is TWikiGuest.
-<
<
+ Users can be authenticated using Basic Authentication or SSL. TWikiUserAuthentication is required in order to track user identities.
->
>
+ Users can be authenticated using Basic Authentication (htaccess) or SSL (secure server). In either case, TWikiUserAuthentication is required in order to track user identities, and use User and Group access control.
   Managing Groups
-<
<
+Groups are defined by group topics in the Main web, like the TWikiAdminGroup. To create a new group:

 Start in TWikiGroups and create a new topic with a name that ends in Group. Example:
->
>
+Groups are defined by group topics created in the Main web, like the TWikiAdminGroup. To create a new group:

 Edit TWikiGroups by entering a new topic with a name that ends in Group. Example:
  SomeGroup
-<
<
+ Define two variables in the group topic:

 Set GROUP = < list of users and/or groups >

 Set ALLOWTOPICCHANGE = < list of users and/or groups >






 A variables is defined as a bullet of format Set NAME = value. A bullet line starts with a multiple of three spaces, an asterisk, and a space.

 The GROUP variable is a comma-separated list of users and/or other groups. Example:

 Set GROUP = Main.SomeUser, Main.OtherUser, Main.SomeOtherGroup



 ALLOWTOPICCHANGE defines who is allowed to change the group topic; it is a comma delimited list of users and groups. You typically want to restrict that to the members of the group itself, so it should contain the name of the topic. (This prevents users not in the group from editing the topic and from gaining unauthorized membership to the group.) For example, for the TWikiAdminGroup topic write:
->
>
+ Set Preferences for two Variables in the new group topic:

 Set GROUP = < list of Users and/or Groups >

 Set ALLOWTOPICCHANGE = < list of Users and/or Groups >

 The GROUP variable is a comma-separated list of Users and/or other Groups. Example:

 Set GROUP = Main.SomeUser, Main.OtherUser, Main.SomeGroup



 ALLOWTOPICCHANGE defines who is allowed to change the group topic; it is a comma delimited list of Users and Groups. You typically want to restrict that to the members of the group itself, so it should contain the name of the topic. (This prevents Users not in the Group from editing the topic to give themselves or others access. For example, for the TWikiAdminGroup topic write:
  Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup





  Restricting Write Access
 Denying editing of a topic also restricts file attachment; both privileges are assigned together.

 Define one or both of these variables in a topic, preferably at the end of the page:
-<
<
+ Set DENYTOPICCHANGE = < list of users and groups >

 Set ALLOWTOPICCHANGE = < list of users and groups >
->
>
+ Set DENYTOPICCHANGE = < list of Users and Groups >

 Set ALLOWTOPICCHANGE = < list of Users and Groups >
-<
<
+ DENYTOPICCHANGE defines users or groups that are not allowed to make changes to the topic. It is a comma delimited list of users and groups. Example:
->
>
+ DENYTOPICCHANGE defines Users or Groups that are not allowed to make changes to the topic, with a comma-delimited list. Example:
  Set DENYTOPICCHANGE = Main.SomeBadBoy, Main.SomeBadGirl, Main.SomeHackerGroup
-<
<
+ ALLOWTOPICCHANGE defines users or groups that are allowed to make changes to the topic. It is a comma delimited list of users and groups. Example:
->
>
+ ALLOWTOPICCHANGE defines Users or Groups that are allowed to make changes to the topic. It is a comma delimited list of Users and Groups. Example:
  Set ALLOWTOPICCHANGE = Main.SomeGoodGuy, Main.SomeGoodGirl, Main.TWikiAdminGroup






 DENYTOPICCHANGE is evaluated before ALLOWTOPICCHANGE. Access is denied if the authenticated person is in the DENYTOPICCHANGE list, or not in the ALLOWTOPICCHANGE list. Access is granted in case DENYTOPICCHANGE and ALLOWTOPICCHANGE is not defined.
 Restricting web-level editing blocks creating new topics, changing topics or attaching files.


 Define one or both of these variable in the WebPreferences topic:
-<
<
+ Set DENYWEBCHANGE = < list of users and groups >

 Set ALLOWWEBCHANGE = < list of users and groups >
->
>
+ Set DENYWEBCHANGE = < list of Users and Groups >

 Set ALLOWWEBCHANGE = < list of Users and Groups >
 The same rules apply as for restricting topics, with these additions:

 DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in WebPreferences)
 To allow a user to rename, move or delete a topic, they also need write (editing) permission.  They also need write access to change references in referring topics.


 Define one or both of these variables in a topic, preferably at the end of the topic:
-<
<
+ Set DENYTOPICRENAME = < list of users and groups >

 Set ALLOWTOPICRENAME = < list of users and groups >
->
>
+ Set DENYTOPICRENAME = < list of Users and Groups >

 Set ALLOWTOPICRENAME = < list of Users and Groups >
-<
<
+ DENYTOPICCRENAME defines users or groups that are not allowed to rename the topic. It is a comma delimited list of users and groups. Example:
->
>
+ DENYTOPICCRENAME defines Users or Groups that are not allowed to rename the topic. It is a comma delimited list of Users and Groups. Example:
  Set DENYTOPICRENAME = Main.SomeBadBoy, Main.SomeBadGirl, Main.SomeHackerGroup
-<
<
+ ALLOWTOPICRENAME defines users or groups that are allowed to rename the topic. It is a comma delimited list of users and groups. Example:
->
>
+ ALLOWTOPICRENAME defines Users or Groups that are allowed to rename the topic. It is a comma delimited list of Users and Groups. Example:
  Set ALLOWTOPICRENAME = Main.SomeGoodGuy, Main.SomeGoodGirl, Main.TWikiAdminGroup






 DENYTOPICRENAME is evaluated before ALLOWTOPICRENAME. Access is denied if the authenticated person is in the DENYTOPICRENAME list, or not in the ALLOWTOPICRENAME list. Access is granted in case DENYTOPICRENAME and ALLOWTOPICRENAME is not defined.
 You can define restrictions of who is allowed to rename a GNHLUG web.


 Define one or both of these variable in the WebPreferences topic:
-<
<
+ Set DENYWEBRENAME = < list of users and groups >

 Set ALLOWWEBRENAME = < list of users and groups >
->
>
+ Set DENYWEBRENAME = < list of Users and Groups >

 Set ALLOWWEBRENAME = < list of Users and Groups >
 The same rules apply as for topics, with these additions:

 DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in WebPreferences)
   Restricting Web Access
-<
<
+You can prevent selected users and groups from accessing certain webs, by hiding them using restricting read access, or by requiring login. There are two basic methods, one simple, using standard preferences variables to hide a web, but offering low security, and a secure log-in approach that is currently a workaround, involving some minor script and filesystem modification.
->
>
+You can prevent selected Users and Groups from accessing certain webs, by hiding them using restricting read access, or by requiring login. There are two basic methods, one simple, using standard preferences variables to hide a web, but offering low security, and a secure log-in approach that is currently a workaround, involving some minor script and filesystem modification.
   Create Hidden Webs
-<
<
+You can prevent selected users and groups from viewing certain GNHLUG webs by setting one or both of these variables in each web's WebPreferences topic:

 Set DENYWEBVIEW = < list of users and groups >

 Set ALLOWWEBVIEW = < list of users and groups >
->
>
+You can prevent selected Users and Groups from viewing certain GNHLUG webs by setting one or both of these variables in each web's WebPreferences topic:

 Set DENYWEBVIEW = < list of Users and Groups >

 Set ALLOWWEBVIEW = < list of Users and Groups >
  If keeping a hidden web out of general use is a consideration, you can prevent the all webs search option from accessing hidden webs, by enabling the NOSEARCHALL variable in WebPreferences:

 Set NOSEARCHALL = on

 It is not recommended to restrict view access to individual topics since all content is searchable within a web.
-<
<
+ This method only works if the view script is authenticated, which means that all users have to login, even for read-only access. (An open guest account, like TWikiGuest, can get around this, allowing anyone to login to a common account with, for example, view-only access for public webs.) TWikiInstallationGuide has more on Basic Authentication, using the .htaccess file.
->
>
+ This method only works if the view script is authenticated, which means that all Users have to login, even for read-only access. (An open guest account, like TWikiGuest, can get around this, allowing anyone to login to a common account with, for example, view-only access for public webs.) TWikiInstallationGuide has more on Basic Authentication, using the .htaccess file.
  Hiding webs is not very secure, as there is a way to circumvent the read access restriction. It can be useful in certain situations - for example, to simplify site organization and clutter, by hiding low traffic webs - but is not recommended for securing sensitive content. (See the next section for a more secure approach.)
  When a user accesses a web where you enabled view restriction, GNHLUG will redirect from the view script to the viewauth script once (this happens only if the user has never edited a topic). Doing so will ask for authentication. The viewauth script shows the requested topic if the user could log on and if the user is authorized to see that web.

 If you enable view restriction for a web, it is recommended to restrict search "all webs" from searching this web. Enable this restriction with the NOSEARCHALL variable in its WebPreferences, like:

 Set NOSEARCHALL = on
-<
<
+ It is not recommended to restrict view access to individual topics since all content is searchable within a web.
->
>
+ It is not recommended to restrict view access to individual topics since all content is searchable within a web - a search will turn up the "hidden" topic.
   Hiding Control Settings 


  To hide access control settings from normal browser viewing, place them in comment markers. 



   <!--
-<
<
+   Set DENYTOPICCHANGE = Main.SomeGroup
->
>
+ Set DENYTOPICCHANGE = Main.SomeGroup
    -->
   The SuperAdminGroup 

By mistyping a user or group name in the ALLOWTOPICCHANGE setting, it's possible to lock a topic so that no-one can edit it from a browser. To avoid this, you can create Web-based superusers:
-<
<
+ Set the $superAdminGroup variable in lib/TWiki.cfg to the name of a group of users who are always allowed to edit/view topics.
->
>
+ Set the $superAdminGroup variable in lib/TWiki.cfg to the name of a group of Users who are always allowed to edit/view topics.
 $superAdminGroup = "TWikiAdminGroup";
  The default setting is not to have superusers.
-<
<
+-- MikeMannix - 01 Apr 2002 

-- PeterThoeny - 04 May 2002
->
>
+-- PeterThoeny - 04 May 2002

-- MikeMannix - 12 May 2002

<<O>> Difference Topic TWikiAccessControl (r1.23 - 04 May 2002 - PeterThoeny)

 TOC: No TOC in "TWiki.TWikiAccessControl"
  Peer editing - the ability to rearrange anything on a page - keeps topics focussed.




 All content is preserved under revision control.
-<
<
+ Edits can be undone by the TWikiAdminGroup (the default administrators group; see #ManagingGroups).
->
>
+ Edits can be undone by the TWikiAdminGroup (the default administrators group; see #ManagingGroups).
  Users are encouraged to edit and refactor (condense a long topic), since there's a safety net.





As a collaboration guideline:
   Managing Groups
-<
<
+Groups are defined by group topics in the Main web, like the TWikiAdminGroup. To start a new group:

 Create a new topic with A name that ends in Group, SomeGroup

 Define two variables:

 Set GROUP = < list of users and groups >

 Set ALLOWTOPICCHANGE = < list of users and groups >






 GROUP is a comma-separated list of users and of other groups:

         Set GROUP = Main.SomeUser, Main.OtherUser, Main.SomeOtherGroup




 ALLOWTOPICCHANGE defines who is allowed to change the group topic; it is a comma delimited list of users and groups. You typically want to restrict that to the members of the group itself, so it should contain the name of the topic,
 
         Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup 
 
     for the TWikiAdminGroup topic. (This prevents users not in the group from editing the topic and from gaining unauthorized membership to the group.)
->
>
+Groups are defined by group topics in the Main web, like the TWikiAdminGroup. To create a new group:

 Start in TWikiGroups and create a new topic with a name that ends in Group. Example:

 SomeGroup



 Define two variables in the group topic:

 Set GROUP = < list of users and/or groups >

 Set ALLOWTOPICCHANGE = < list of users and/or groups >






 A variables is defined as a bullet of format Set NAME = value. A bullet line starts with a multiple of three spaces, an asterisk, and a space.

 The GROUP variable is a comma-separated list of users and/or other groups. Example:

 Set GROUP = Main.SomeUser, Main.OtherUser, Main.SomeOtherGroup



 ALLOWTOPICCHANGE defines who is allowed to change the group topic; it is a comma delimited list of users and groups. You typically want to restrict that to the members of the group itself, so it should contain the name of the topic. (This prevents users not in the group from editing the topic and from gaining unauthorized membership to the group.) For example, for the TWikiAdminGroup topic write:

 Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup
   Restricting Write Access
 Denying editing of a topic also restricts file attachment; both privileges are assigned together.

 Define one or both of these variables in a topic, preferably at the end of the page:
-<
<
+ Set DENYTOPICCHANGE = < list of users and groups >

 Set ALLOWTOPICCHANGE = < list of users and groups >
->
>
+ Set DENYTOPICCHANGE = < list of users and groups >

 Set ALLOWTOPICCHANGE = < list of users and groups >
-<
<
+ DENYTOPICCHANGE defines users or groups that are not allowed to make changes to the topic. It is a comma delimited list of users and groups. Example: 
     * Set DENYTOPICCHANGE = Main.SomeBadBoy, Main.SomeBadGirl, Main.SomeHackerGroup
->
>
+ DENYTOPICCHANGE defines users or groups that are not allowed to make changes to the topic. It is a comma delimited list of users and groups. Example:

 Set DENYTOPICCHANGE = Main.SomeBadBoy, Main.SomeBadGirl, Main.SomeHackerGroup
-<
<
+ ALLOWTOPICCHANGE defines users or groups that are allowed to make changes to the topic. It is a comma delimited list of users and groups. Example: 
     * Set ALLOWTOPICCHANGE = Main.SomeGoodGuy, Main.SomeGoodGirl, Main.TWikiAdminGroup
->
>
+ ALLOWTOPICCHANGE defines users or groups that are allowed to make changes to the topic. It is a comma delimited list of users and groups. Example:

 Set ALLOWTOPICCHANGE = Main.SomeGoodGuy, Main.SomeGoodGirl, Main.TWikiAdminGroup
  DENYTOPICCHANGE is evaluated before ALLOWTOPICCHANGE. Access is denied if the authenticated person is in the DENYTOPICCHANGE list, or not in the ALLOWTOPICCHANGE list. Access is granted in case DENYTOPICCHANGE and ALLOWTOPICCHANGE is not defined.
 Restricting web-level editing blocks creating new topics, changing topics or attaching files.


 Define one or both of these variable in the WebPreferences topic:
-<
<
+ Set DENYWEBCHANGE = < list of users and groups >

 Set ALLOWWEBCHANGE = < list of users and groups >
->
>
+ Set DENYWEBCHANGE = < list of users and groups >

 Set ALLOWWEBCHANGE = < list of users and groups >
 The same rules apply as for restricting topics, with these additions:

 DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in WebPreferences)
 To allow a user to rename, move or delete a topic, they also need write (editing) permission.  They also need write access to change references in referring topics.


 Define one or both of these variables in a topic, preferably at the end of the topic:
-<
<
+ Set DENYTOPICRENAME = < list of users and groups >

 Set ALLOWTOPICRENAME = < list of users and groups >
->
>
+ Set DENYTOPICRENAME = < list of users and groups >

 Set ALLOWTOPICRENAME = < list of users and groups >
-<
<
+ DENYTOPICCRENAME defines users or groups that are not allowed to rename the topic. It is a comma delimited list of users and groups. Example: 
     * Set DENYTOPICRENAME = Main.SomeBadBoy, Main.SomeBadGirl, Main.SomeHackerGroup
->
>
+ DENYTOPICCRENAME defines users or groups that are not allowed to rename the topic. It is a comma delimited list of users and groups. Example:

 Set DENYTOPICRENAME = Main.SomeBadBoy, Main.SomeBadGirl, Main.SomeHackerGroup
-<
<
+ ALLOWTOPICRENAME defines users or groups that are allowed to rename the topic. It is a comma delimited list of users and groups. Example: 
     * Set ALLOWTOPICRENAME = Main.SomeGoodGuy, Main.SomeGoodGirl, Main.TWikiAdminGroup
->
>
+ ALLOWTOPICRENAME defines users or groups that are allowed to rename the topic. It is a comma delimited list of users and groups. Example:

 Set ALLOWTOPICRENAME = Main.SomeGoodGuy, Main.SomeGoodGirl, Main.TWikiAdminGroup
  DENYTOPICRENAME is evaluated before ALLOWTOPICRENAME. Access is denied if the authenticated person is in the DENYTOPICRENAME list, or not in the ALLOWTOPICRENAME list. Access is granted in case DENYTOPICRENAME and ALLOWTOPICRENAME is not defined.
 You can define restrictions of who is allowed to rename a GNHLUG web.


 Define one or both of these variable in the WebPreferences topic:
-<
<
+ Set DENYWEBRENAME = < list of users and groups >

 Set ALLOWWEBRENAME = < list of users and groups >
->
>
+ Set DENYWEBRENAME = < list of users and groups >

 Set ALLOWWEBRENAME = < list of users and groups >
 The same rules apply as for topics, with these additions:

 DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in WebPreferences)
   Create Hidden Webs 

You can prevent selected users and groups from viewing certain GNHLUG webs by setting one or both of these variables in each web's WebPreferences topic:
-<
<
+ Set DENYWEBVIEW = < list of users and groups >

 Set ALLOWWEBVIEW = < list of users and groups >
->
>
+ Set DENYWEBVIEW = < list of users and groups >

 Set ALLOWWEBVIEW = < list of users and groups >
  If keeping a hidden web out of general use is a consideration, you can prevent the all webs search option from accessing hidden webs, by enabling the NOSEARCHALL variable in WebPreferences:
-<
<
+ Set NOSEARCHALL = on
->
>
+ Set NOSEARCHALL = on
  It is not recommended to restrict view access to individual topics since all content is searchable within a web.

 This method only works if the view script is authenticated, which means that all users have to login, even for read-only access. (An open guest account, like TWikiGuest, can get around this, allowing anyone to login to a common account with, for example, view-only access for public webs.) TWikiInstallationGuide has more on Basic Authentication, using the .htaccess file.
   Create Authenticated Access By Web
-<
<
+ THIS SECTION CONTAINS WORKAROUNDS. Perhaps unconventional for official documentation, but practical, the following method for extending TWiki functionality involves modifying core TWiki, making it essentially not a feature but a hack. Still, it is officially TWiki developer-approved and documented, and will no doubt be included in some form in an upcoming edition of TWiki. 

To selectively restrict web access with the security of Basic Authentication, there is a reliable workaround that involves some straightforward code modification:

 Set aside the view script (rename) and create a view subdirectory in its place.

 In the view subdirectory, create a separate copy of a modified viewing script for each web, and create .htaccess settings for the restricted webs.

  You can use symbolic links to a single copy of the viewing script to make any script updates that much easier.






Example of viewing script redirect
#!/usr/bin/perl -w
#

chdir '..';

# Adjust SCRIPT and PATH_INFO variables to account for the changed directory
my $web = $ENV{SCRIPT_NAME};
$web    =~ s#^.*/view(/[^/]*).*$#$1#; # isolate the path element after "view"
$ENV{PATH_TRANSLATED} =~ s#(/[^/]*)$#$web$1#;
$ENV{PATH_INFO}       =~ s#(/[^/]*)$#$web$1#;
$ENV{SCRIPT_NAME}     =~ s#/view$web#/view#;
$ENV{SCRIPT_FILENAME} =~ s#/view$web#/view#;

# open (LOG, '>>/tmp/redirect.log');
# print LOG join ("\n", scalar localtime (time ()), %ENV);
# close LOG;
exec ('/usr/bin/perl', '-wT', 'view.orig') or

print <<EOF;
Content-type: text/plain

Error executing /cgi-bin/view.orig: $?
Click the BACK button in your browser and contact webmaster\@bcs-oops.org.

EOF



 (mod by ImmoHuneke^? - 16 Mar 2002)



A SECOND OPTION: A less reliable workaround that doesn't involve code changes, but does require renaming a script, can provide the same generally unrestricted viewing access, with authentication only on selected webs:
->
>
+Use the following setup to provide unrestricted viewing access to open webs, with authentication only on selected webs:
  Omit the view script from the .htaccess file.

 Enable the $doRememberRemoteUser flag in lib/TWiki.cfg as described in TWikiUserAuthentication. GNHLUG will now remember the IP address of an authenticated user. 

 Copy the view script to viewauth (or better, create a symbolic link) 

 Add viewauth to the list of authenticated scripts in the .htaccess file.
->
>
  When a user accesses a web where you enabled view restriction, GNHLUG will redirect from the view script to the viewauth script once (this happens only if the user has never edited a topic). Doing so will ask for authentication. The viewauth script shows the requested topic if the user could log on and if the user is authorized to see that web.

 If you enable view restriction for a web, it is recommended to restrict search "all webs" from searching this web. Enable this restriction with the NOSEARCHALL variable in its WebPreferences, like:
-<
<
+ Set NOSEARCHALL = on
->
>
+ Set NOSEARCHALL = on
  It is not recommended to restrict view access to individual topics since all content is searchable within a web.





  Hiding Control Settings
  The default setting is not to have superusers.
-<
<
+-- MikeMannix - 01 Apr 2002
->
>
+-- MikeMannix - 01 Apr 2002 

-- PeterThoeny - 04 May 2002

<<O>> Difference Topic TWikiAccessControl (r1.22 - 01 Apr 2002 - MikeMannix)

Line: 57 to 57
	TOC: No TOC in "TWiki.TWikiAccessControl"
	Deny Editing by Topic
Changed:
< <	Denying editing of a topic also restricts attaching files to it; both privileges are assigned together.
> >	Denying editing of a topic also restricts file attachment; both privileges are assigned together.
	Define one or both of these variables in a topic, preferably at the end of the page: Set DENYTOPICCHANGE = < list of users and groups > Set ALLOWTOPICCHANGE = < list of users and groups >
Line: 119 to 119
	You can prevent selected users and groups from viewing certain GNHLUG webs by setting one or both of these variables in each web's WebPreferences topic: Set DENYWEBVIEW = < list of users and groups > Set ALLOWWEBVIEW = < list of users and groups >
Changed:
< <	If keeping a hidden web out of general use is a consideration, you should also prevent the "all webs" search option from accessing each hidden web, by enabling the `NOSEARCHALL` variable in WebPreferences:
> >	If keeping a hidden web out of general use is a consideration, you can prevent the `all webs` search option from accessing hidden webs, by enabling the `NOSEARCHALL` variable in WebPreferences:
	Set NOSEARCHALL = on It is not recommended to restrict view access to individual topics since all content is searchable within a web.
Changed:
< <	This method only works if the `view` script is authenticated, which means that all users have to login, even for read-only access. (An open guest account, like TWikiGuest, can get around this, allowing anyone to login with, for example, view-only access for public webs.) TWikiInstallationGuide has more on Basic Authentication, using the `.htaccess` file. Hiding webs is not very secure, as there is a way to circumvent the read access restriction. It can be useful in certain situations - for example, to simplify site organization and clutter, by hiding low traffic webs - but is not recommended for securing sensitive content.
> >	This method only works if the `view` script is authenticated, which means that all users have to login, even for read-only access. (An open guest account, like TWikiGuest, can get around this, allowing anyone to login to a common account with, for example, view-only access for public webs.) TWikiInstallationGuide has more on Basic Authentication, using the `.htaccess` file. Hiding webs is not very secure, as there is a way to circumvent the read access restriction. It can be useful in certain situations - for example, to simplify site organization and clutter, by hiding low traffic webs - but is not recommended for securing sensitive content. (See the next section for a more secure approach.)
	Create Authenticated Access By Web
Changed:
< <	To selectively restrict web access with the security of Basic Authentication, there is a reliable workaround that involves some straightforward code modification:
> >	*THIS SECTION CONTAINS WORKAROUNDS.* Perhaps unconventional for official documentation, but practical, the following method for extending TWiki functionality involves modifying core TWiki, making it essentially not a feature but a hack. Still, it is officially TWiki developer-approved and documented, and will no doubt be included in some form in an upcoming edition of TWiki. To selectively restrict web access with the security of Basic Authentication, there is a reliable workaround that involves some straightforward code modification:
	Set aside the `view` script (rename) and create a `view` subdirectory in its place. In the `view` subdirectory, create a separate copy of a modified viewing script for each web, and create `.htaccess` settings for the restric

Authentication vs. Access Control

Users and Groups

Managing Users

Managing Groups

Hiding Control Settings

The SuperAdminGroup

Restricting Web Access

Restricting Read Access

Create Hidden Webs

Deny Viewing by Topic

Deny Viewing by Web

Obfuscate Webs

Authenticate all Webs and Restrict Selected Webs

Create Authenticated Access By Web

Authenticate and Restricting Selected Webs Only

Hiding Control Settings

TWiki Access Control

An Important Control Consideration

Users and Groups

Managing Users

Managing Groups

Restricting Write Access

Restricting Web Access

Create Hidden Webs

Hiding Control Settings

The SuperAdminGroup

Managing Groups

Restricting Write Access

Create Hidden Webs

Create Authenticated Access By Web

Hiding Control Settings

Deny Editing by Topic

Create Authenticated Access By Web