1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
%TOC% %STARTINCLUDE%
## <a name="TWiki_Access_Control"> TWiki Access Control </a>
_Restricting read and write access to topics and webs, by users and groups_
### <a name="Overview"> Overview </a>
%WIKITOOLNAME% allows you to define restrictions of who is allowed to view a %WIKITOOLNAME% web, make changes to topics or attach files.
**IMPORTANT NOTE:** Think twice before restricting read or write access to a web or a topic, because an open system where everybody can contribute is the essence of the %TWIKIWEB%.WikiCulture. Experience shows that unrestricted write access works very well because:
* Peer influence is enough to ensure that only relevant content is posted.
* Peer editing - edit anything on a page - keeps topics focussed.
* All content is preserved under revision control.
* Edits can be undone by the %MAINWEB%.TWikiAdminGroup (the default administrators group; see Managing Groups).
* Editing and refactoring (condensing a long topic) is encouraged (there's a safety net).
### <a name="Users_and_Groups"> Users and Groups </a>
Access control is based on users and groups.
#### <a name="Managing_Users"> Managing Users </a>
A user is created by with the TWikiRegistration form. The process generates a topic in the %MAINWEB% web in the new user's [[WikiName]]. The default visitor name is %MAINWEB%.TWikiGuest.
* Users can be authenticated using Basic Authentication or SSL. [[TWikiDocumentation]] has more.
<a name="ManagingGroups"></a>
#### <a name="Managing_Groups"> Managing Groups </a>
Groups are defined by group topics in the %MAINWEB% web, like the %MAINWEB%.TWikiAdminGroup.
* A group topic name must end in **\_Group**
* The group topic should define these two variables:
> * * Set GROUP = < list of users and groups >
> * Set ALLOWTOPICCHANGE = < list of users and groups >
* GROUP defines the members of the group; it is a comma delimited list of users and other groups. Example: <br /><code>** \* Set GROUP = %MAINWEB%.SomeUser, %MAINWEB%.OtherUser, %MAINWEB%.SomeOtherGroup**</code>
* 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, i.e. <br /><code> \* Set ALLOWTOPICCHANGE = %MAINWEB%.TWikiAdminGroup</code><br /> for the TWikiAdminGroup topic. (This is to prevent users not in the group from editing the topic and gaining unauthorized membership to the group.)
### <a name="Restricting_Write_Access"> Restricting Write Access </a>
#### <a name="Deny_Editing_by_Topic"> Deny Editing by Topic </a>
You can define restrictions of who is allowed to make changes to a topic or attach files to it.
Define one or both of these variables in a topic, preferably at the end of the topic:
* 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: <br /><code> \* Set DENYTOPICCHANGE = %MAINWEB%.SomeBadBoy, %MAINWEB%.SomeBadGirl, %MAINWEB%.SomeHackerGroup</code>
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: <br /><code> \* Set ALLOWTOPICCHANGE = %MAINWEB%.SomeGoodGuy, %MAINWEB%.SomeGoodGirl, %MAINWEB%.TWikiAdminGroup</code>
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.
#### <a name="Deny_Editing_by_Web"> Deny Editing by Web </a>
You can define restrictions of who is allowed to make changes to a %WIKITOOLNAME% web. This includes creating new topics, changing topics or attaching files.
Define one or both of these variable in the %WEBPREFSTOPIC% topic:
* Set DENYWEBCHANGE = < list of users and groups >
* Set ALLOWWEBCHANGE = < list of users and groups >
The same rules apply like the one for Access Control for Individual Topics; with these additions:
* DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in %WEBPREFSTOPIC%)
* ALLOWTOPICCHANGE (in topic) overrides ALLOWWEBCHANGE (in %WEBPREFSTOPIC%)
### <a name="Restricting_Rename_Access"> Restricting Rename Access </a>
#### <a name="Deny_Renaming_by_Topic"> Deny Renaming by Topic </a>
You can define restrictions of who is allowed to rename a topic. Note that users need this permission in addition to the CHANGE permission in order to rename a topic. They also need CHANGE 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 >
DENYTOPICCRENAME defines users or groups that **are not** allowed to rename the topic. It is a comma delimited list of users and groups. Example: <br /><code> \* Set DENYTOPICRENAME = %MAINWEB%.SomeBadBoy, %MAINWEB%.SomeBadGirl, %MAINWEB%.SomeHackerGroup</code>
ALLOWTOPICRENAME defines users or groups that **are** allowed to rename the topic. It is a comma delimited list of users and groups. Example: <br /><code> \* Set ALLOWTOPICRENAME = %MAINWEB%.SomeGoodGuy, %MAINWEB%.SomeGoodGirl, %MAINWEB%.TWikiAdminGroup</code>
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.
#### <a name="Deny_Renaming_by_Web"> Deny Renaming by Web </a>
You can define restrictions of who is allowed to do renames for a %WIKITOOLNAME% web.
Define one or both of these variable in the %WEBPREFSTOPIC% topic:
* Set DENYWEBRENAME = < list of users and groups >
* Set ALLOWWEBRENAME = < list of users and groups >
The same rules apply like the one for Access Control for Individual Topics; with these additions:
* DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in %WEBPREFSTOPIC%)
* ALLOWTOPICRENAME (in topic) overrides ALLOWWEBRENAME (in %WEBPREFSTOPIC%)
### <a name="Restricting_Read_Access"> Restricting Read Access </a>
You can define restrictions of who is allowed to view a %WIKITOOLNAME% web.
Define one or both of these variable in the %WEBPREFSTOPIC% topic:
* Set DENYWEBVIEW = < list of users and groups >
* Set ALLOWWEBVIEW = < list of users and groups >
#### <a name="Known_Issues"> Known Issues </a>
* The view restriction is not suitable for very sensitive content since there is a way to circumvent the read access restriction.
* Read access restriction only works if the view script is authenticated, that means that users need to log on also just to read topics. [[TWikiDocumentation]] has more on Basic Authentication based on the <code>**.htaccess**</code> file.
##### <a name="Selective_Unrestricted_Web_Acces"> Selective Unrestricted Web Access </a>
* There is a workaround if you prefer to have unrestricted access to view topics located in normal webs, and to authenticate users only for webs where view restriction is enabled:
* Leave the <code>**view**</code> script non-authenticated in the `.htaccess` file.
* Enable the <code>**$doRememberRemoteUser**</code> flag in <code>**lib/wikicfg.pm**</code> as described in [[TWikiDocumentation]]. %WIKITOOLNAME% will now remember the IP address of an authenticated user.
* Copy the <code>**view**</code> script to <code>**viewauth**</code> (or better, create a symbolic link)
* Add <code>**viewauth**</code> to the list of authenticated scripts in the .htaccess file.
* When a user accesses a web where you enabled view restriction, %WIKITOOLNAME% 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 <code>**NOSEARCHALL**</code> 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 name="SuperAdminGroup"></a>
### <a name="The_SuperAdminGroup"> The SuperAdminGroup </a>
The above schema can lock completely a topic in case of a typing error of the ALLOWTOPICCHANGE setting (see [[TWikiCodevUnchangeableTopicBug]] for more detail). To avoid this:
* Set the <code>**$superAdminGroup**</code> variable in <code>**lib/TWiki.cfg**</code> to the name of a group of users that are always allowed to edit/view topics.
$superAdminGroup = "TWikiAdminGroup";
* The default setting is not to have superusers.
-- [[PeterThoeny]] - 16 Mar 2001 <br /> -- [[AndreaSterbini]] - 11 Apr 2001 <br /> %STOPINCLUDE% **_Related topics:_** %WIKIPREFSTOPIC%, %WEBPREFSTOPIC% (in every web), %MAINWEB%.TWikiAdminGroup, %MAINWEB%.TWikiGroups
|
