|
TOC: No TOC in "Tweak.TWikiAccessControl"
|
|
Overview
|
|
<
< |
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 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.
|
|
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 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:
|
|
- 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.
- All content is preserved under revision control.
|
|
<
< |
-
- Edits can be undone by the TWikiAdminGroup? (the default administrators group; see Managing Groups).
|
>
> |
-
- 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 Users
|
|
<
< |
A user is created by with the TWikiRegistration form. The process generates a topic in the Faemalia web in the new user's WikiName. The default visitor name is TWikiGuest.
|
>
> |
A user is created by with the TWikiRegistration form. The process generates a topic in the Faemalia web in the new user's WikiName. The default visitor name is TWikiGuest.
|
|
|
|
<
< |
- Users can be authenticated using Basic Authentication or SSL. Authentication is required in order to track user identities.
|
>
> |
- Users can be authenticated using Basic Authentication or SSL. TWikiUserAuthentication is required in order to track user identities.
|
|
Managing Groups
|
|
Known Issues
- 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. TWiki Installation Guide has more on Basic Authentication based on the
.htaccess file.
|
>
> |
- Read access restriction only works if the view script is authenticated, that means that users need to log on also just to read topics. TWikiInstallationGuide has more on Basic Authentication based on the
.htaccess file.
|
|
Selective Unrestricted Web Access
- 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:
- Omit the
view script from the .htaccess file.
|
|
<
< |
-
- Enable the
$doRememberRemoteUser flag in lib/wikicfg.pm as described in User Authentication. TWiki will now remember the IP address of an authenticated user.
|
>
> |
-
- Enable the
$doRememberRemoteUser flag in lib/TWiki.cfg as described in TWikiUserAuthentication. TWiki 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, TWiki 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.
|
|
TOC: No TOC in "Tweak.TWikiAccessControl"
|
|
<
< |
TWiki Access Control
|
>
> |
TWiki Access Control
|
|
Restricting read and write access to topics and webs, by users and groups
|
|
<
< |
Overview
|
>
> |
Overview
|
|
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.
|
|
<
< |
An Important Control Consideration
|
>
> |
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:
|
|
- Create broad groups (more and varied input), and...
- Avoid creating view-only users (if you can read it, you can contribute to it).
|
|
<
< |
Users and Groups
|
>
> |
Users and Groups
|
|
Access control is based on users and groups. Users are defined by their WikiNames, an then organized into unlimited combinations under different user groups.
|
|
<
< |
Managing Users
|
>
> |
Managing Users
|
|
A user is created by with the TWikiRegistration form. The process generates a topic in the Faemalia web in the new user's WikiName. The default visitor name is TWikiGuest.
- Users can be authenticated using Basic Authentication or SSL. Authentication is required in order to track user identities.
|
|
<
< |
Managing Groups
|
>
> |
Managing Groups
|
|
Groups are defined by group topics in the Faemalia web, like the TWikiAdminGroup?. To start a new group:
- Create a new topic with A name that ends in Group,
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,
* Set ALLOWTOPICCHANGE = Faemalia.TWikiAdminGroup
for the TWikiAdminGroup topic. (This prevents users not in the group from editing the topic and from gaining unauthorized membership to the group.)
|
|
<
< |
Restricting Write Access
|
>
> |
Restricting Write Access
|
|
You can define who is allowed to make changes to a web or a topic.
|
|
<
< |
Deny Editing by Topic
|
>
> |
Deny Editing by Topic
|
|
Denying editing of a topic also restricts attaching files to it; both privileges are assigned together.
- Define one or both of these variables in a topic, preferably at the end of the page:
|
|
- 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.
|
|
<
< |
Deny Editing by Web
|
>
> |
Deny Editing by Web
|
|
Restricting web-level editing blocks creating new topics, changing topics or attaching files.
|
|
- DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in WebPreferences)
- ALLOWTOPICCHANGE (in topic) overrides ALLOWWEBCHANGE (in WebPreferences)
|
|
<
< |
Restricting Rename Access
|
>
> |
Restricting Rename Access
|
|
You can define who is allowed to rename, move or delete a topic, or rename a web.
|
|
<
< |
Deny Renaming by Topic
|
>
> |
Deny Renaming by Topic
|
|
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.
|
|
- 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.
|
|
<
< |
Deny Renaming by Web
|
>
> |
Deny Renaming by Web
|
|
You can define restrictions of who is allowed to rename a TWiki web.
|
|
- DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in WebPreferences)
- ALLOWTOPICRENAME (in topic) overrides ALLOWWEBRENAME (in WebPreferences)
|
|
<
< |
Restricting Read Access
|
>
> |
Restricting Read Access
|
|
You can define restrictions of who is allowed to view a TWiki web.
|
|
-
- Set DENYWEBVIEW = < list of users and groups >
- Set ALLOWWEBVIEW = < list of users and groups >
|
|
<
< |
Known Issues
|
>
> |
Known Issues
|
|
- 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. TWiki Installation Guide has more on Basic Authentication based on the
.htaccess file.
|
|
<
< |
Selective Unrestricted Web Access
|
>
> |
Selective Unrestricted Web Access
|
|
- 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:
- Omit the
view script from the .htaccess file.
|
|
-
-
- It is not recommended to restrict view access to individual topics since all content is searchable within a web.
|
|
<
< |
The SuperAdminGroup
|
>
> |
The SuperAdminGroup
|
|
By mistyping a user or group name in the ALLOWTOPICCHANGE setting, it's possible to lock a topic so that it no-one can edit it from a browser. To avoid this:
- Set the
$superAdminGroup variable in lib/TWiki.cfg to the name of a group of users that are always allowed to edit/view topics.
|
|
TOC: No TOC in "Tweak.TWikiAccessControl"
|
|
Overview
|
|
<
< |
TWiki allows you to define restrictions of who is allowed to view a TWiki web, make changes to topics or attach files.
|
>
> |
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.
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:
|
|
|
|
<
< |
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 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.
|
>
> |
- 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 Managing Groups).
|
|
<
< |
-
- Editing and refactoring (condensing a long topic) is encouraged (there's a safety net).
|
>
> |
-
- Users are encouraged to edit and refactor (condense a long topic), since there's a safety net.
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).
|
|
Users and Groups
|
|
<
< |
Access control is based on users and groups.
|
>
> |
Access control is based on users and groups. Users are defined by their WikiNames, an then organized into unlimited combinations under different user groups.
|
|
Managing Users
|
|
<
< |
A user is created by with the TWikiRegistration form. The process generates a topic in the Faemalia web in the new user's WikiName. The default visitor name is TWikiGuest.
|
>
> |
A user is created by with the TWikiRegistration form. The process generates a topic in the Faemalia web in the new user's WikiName. The default visitor name is TWikiGuest.
- Users can be authenticated using Basic Authentication or SSL. Authentication is required in order to track user identities.
|
|
Managing Groups
|
|
<
< |
Groups are defined by group topics in the Faemalia web, like the TWikiAdminGroup?.
- A group topic name must end in _Group
- The group topic should define these two variables:
|
>
> |
Groups are defined by group topics in the Faemalia 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 defines the members of the group; it is a comma delimited list of users and other groups. Example:
* Set GROUP = Faemalia.SomeUser, Faemalia.OtherUser, Faemalia.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, i.e.
* Set ALLOWTOPICCHANGE = Faemalia.TWikiAdminGroup
for the TWikiAdminGroup topic. (This is to prevent users not in the group from editing the topic and gaining unauthorized membership to the group.)
|
>
> |
-
- GROUP is a comma-separated list of users and of other groups:
* Set GROUP = Faemalia.SomeUser, Faemalia.OtherUser, Faemalia.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 = Faemalia.TWikiAdminGroup
for the TWikiAdminGroup topic. (This prevents users not in the group from editing the topic and from gaining unauthorized membership to the group.)
|
|
Restricting Write Access
|
|
<
< |
Deny Editing by Topic
|
>
> |
You can define who is allowed to make changes to a web or a topic.
|
|
|
|
<
< |
You can define restrictions of who is allowed to make changes to a topic or attach files to it.
|
>
> |
Deny Editing by Topic
|
|
|
|
<
< |
Define one or both of these variables in a topic, preferably at the end of the topic:
|
>
> |
Denying editing of a topic also restricts attaching files to it; 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 >
|
|
<
< |
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 = Faemalia.SomeBadBoy, Faemalia.SomeBadGirl, Faemalia.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 = Faemalia.SomeBadBoy, Faemalia.SomeBadGirl, Faemalia.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 = Faemalia.SomeGoodGuy, Faemalia.SomeGoodGirl, Faemalia.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 = Faemalia.SomeGoodGuy, Faemalia.SomeGoodGirl, Faemalia.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.
|
>
> |
- 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.
|
|
Deny Editing by Web
|
|
<
< |
You can define restrictions of who is allowed to make changes to a TWiki web. This includes creating new topics, changing topics or attaching files.
|
>
> |
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 >
|
|
<
< |
The same rules apply like the one for Access Control for Individual Topics; with these additions:
|
>
> |
The same rules apply as for restricting topics, with these additions:
|
|
- DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in WebPreferences)
- ALLOWTOPICCHANGE (in topic) overrides ALLOWWEBCHANGE (in WebPreferences)
Restricting Rename Access
|
|
<
< |
|
>
> |
You can define who is allowed to rename, move or delete a topic, or rename a web.
|
|
Deny Renaming by Topic
|
|
<
< |
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.
|
>
> |
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:
|
>
> |
- 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:
* Set DENYTOPICRENAME = Faemalia.SomeBadBoy, Faemalia.SomeBadGirl, Faemalia.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 = Faemalia.SomeBadBoy, Faemalia.SomeBadGirl, Faemalia.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 = Faemalia.SomeGoodGuy, Faemalia.SomeGoodGirl, Faemalia.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 = Faemalia.SomeGoodGuy, Faemalia.SomeGoodGirl, Faemalia.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.
|
>
> |
- 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.
|
|
Deny Renaming by Web
|
|
<
< |
You can define restrictions of who is allowed to do renames for a TWiki web.
|
>
> |
You can define restrictions of who is allowed to rename a TWiki 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 >
|
|
<
< |
The same rules apply like the one for Access Control for Individual Topics; with these additions:
|
>
> |
The same rules apply as for topics, with these additions:
|
|
- DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in WebPreferences)
- ALLOWTOPICRENAME (in topic) overrides ALLOWWEBRENAME (in WebPreferences)
|
|
You can define restrictions of who is allowed to view a TWiki web.
|
|
<
< |
Define one or both of these variable in the WebPreferences topic:
|
>
> |
|
|
- Set DENYWEBVIEW = < list of users and groups >
- Set ALLOWWEBVIEW = < list of users and groups >
|
|
Selective Unrestricted Web Access
- 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
view script non-authenticated in the .htaccess file.
- Enable the
$doRememberRemoteUser flag in lib/wikicfg.pm as described in User Authentication. TWiki 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.
|
>
> |
-
- Omit the
view script from the .htaccess file.
- Enable the
$doRememberRemoteUser flag in lib/wikicfg.pm as described in User Authentication. TWiki 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, TWiki 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:
|
|
The SuperAdminGroup
|
|
<
< |
The above schema can lock completely a topic in case of a typing error of the ALLOWTOPICCHANGE setting (see UnchangeableTopicBug for more detail). To avoid this:
- Set the
$superAdminGroup variable in lib/TWiki.cfg to the name of a group of users that are always allowed to edit/view topics.
|
>
> |
By mistyping a user or group name in the ALLOWTOPICCHANGE setting, it's possible to lock a topic so that it no-one can edit it from a browser. To avoid this:
- Set the
$superAdminGroup variable in lib/TWiki.cfg 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
|
|
TWiki Access Control
|
|
>
> |
Restricting read and write access to topics and webs, by users and groups
Overview
|
|
TWiki allows you to define restrictions of who is allowed to view a TWiki 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 WikiCulture. Experience shows that unrestricted write access works very well because:
|
|
<
< |
- There is enough peer pressure to post only conform content.
- Content does not get lost because topics are under revision control.
- A topic revision can be undone by a member of the TWikiAdminGroup? in case needed.
|
>
> |
- 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 TWikiAdminGroup? (the default administrators group; see Managing Groups).
- Editing and refactoring (condensing a long topic) is encouraged (there's a safety net).
|
|
Users and Groups
Access control is based on users and groups.
|
|
<
< |
Users are defined by the user topics in the Faemalia web, i.e. TWikiGuest
- Users can be authenticated using basic authentication or SSL. Installation Notes has more.
|
>
> |
Managing Users
A user is created by with the TWikiRegistration form. The process generates a topic in the Faemalia web in the new user's WikiName. The default visitor name is TWikiGuest.
Managing Groups
|
|
|
|
<
< |
Groups are defined by group topics in the Faemalia web, i.e. TWikiAdminGroup?
- A group topic name must end in ...Group
|
>
> |
Groups are defined by group topics in the Faemalia web, like the 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:
* Set GROUP = Faemalia.SomeUser, Faemalia.OtherUser, Faemalia.SomeOtherGroup
|
>
> |
- GROUP defines the members of the group; it is a comma delimited list of users and other groups. Example:
* Set GROUP = Faemalia.SomeUser, Faemalia.OtherUser, Faemalia.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, i.e.
* Set ALLOWTOPICCHANGE = Faemalia.TWikiAdminGroup
for the TWikiAdminGroup topic. (This is to prevent users not in the group from editing the topic and gaining unauthorized membership to the group.)
|
|
>
> |
Restricting Write Access
|
|
|
|
<
< |
Write Access Restriction by Topic
|
>
> |
Deny Editing by Topic
|
|
You can define restrictions of who is allowed to make changes to a topic or attach files to it.
|
|
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.
|
|
<
< |
Write Access Restriction by Web
|
>
> |
Deny Editing by Web
|
|
You can define restrictions of who is allowed to make changes to a TWiki web. This includes creating new topics, changing topics or attaching files.
|
|
- DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in WebPreferences)
- ALLOWTOPICCHANGE (in topic) overrides ALLOWWEBCHANGE (in WebPreferences)
|
|
<
< |
Rename Access Restriction by Topic
|
>
> |
Restricting Rename Access
Deny Renaming by Topic
|
|
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.
|
|
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.
|
|
<
< |
Rename Access Restriction by Web
|
>
> |
Deny Renaming by Web
|
|
You can define restrictions of who is allowed to do renames for a TWiki web.
|
|
- DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in WebPreferences)
- ALLOWTOPICRENAME (in topic) overrides ALLOWWEBRENAME (in WebPreferences)
|
|
<
< |
Read Access Restriction by Web
|
>
> |
Restricting Read Access
|
|
You can define restrictions of who is allowed to view a TWiki web.
|
|
- Set DENYWEBVIEW = < list of users and groups >
- Set ALLOWWEBVIEW = < list of users and groups >
|
|
<
< |
Read Restriction Known Issues
|
>
> |
Known Issues
|
|
- 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. TWiki Installation has more on basic authentication based on the
.htaccess file.
|
>
> |
- Read access restriction only works if the view script is authenticated, that means that users need to log on also just to read topics. TWiki Installation Guide has more on Basic Authentication based on the
.htaccess file.
Selective Unrestricted Web Access
|
|
- 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
view script non authenticated in the .htaccess file.
- Enable the
$doRememberRemoteUser flag in wikicfg.pm as described in TWiki Authentication. TWiki 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.
|
>
> |
-
- Leave the
view script non-authenticated in the .htaccess file.
- Enable the
$doRememberRemoteUser flag in lib/wikicfg.pm as described in User Authentication. TWiki 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, TWiki 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:
|
>
> |
- 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:
|
|
|
|
<
< |
- 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.
|
|
The SuperAdminGroup
|
|
<
< |
The above schema can lock completely a topic in case of a typing error of the ALLOWTOPICCHANGE setting (see UnchangeableTopicBug). To avoid this:
- set the
$superAdminGroup variable in TWiki.cfg to the name of a group of users that are always allowed to edit/view topics. E.g.:
|
>
> |
The above schema can lock completely a topic in case of a typing error of the ALLOWTOPICCHANGE setting (see UnchangeableTopicBug for more detail). To avoid this:
- Set the
$superAdminGroup variable in lib/TWiki.cfg 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
|
>
> |
- The default setting is not to have superusers.
|
|
-- PeterThoeny? - 16 Mar 2001
-- AndreaSterbini - 11 Apr 2001
|
|
>
> |
TOC: No TOC in "Tweak.TWikiAccessControl"
|
|
TWiki Access Control
TWiki allows you to define restrictions of who is allowed to view a TWiki web, make changes to topics or attach files.
|
|
- 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.
* Set ALLOWTOPICCHANGE = Faemalia.TWikiAdminGroup
for the TWikiAdminGroup topic. (This is to prevent users not in the group from editing the topic and gaining unauthorized membership to the group.)
|
|
<
< |
Write Access Restriction for Individual Topics
|
>
> |
Write Access Restriction by Topic
|
|
You can define restrictions of who is allowed to make changes to a topic or attach files to it.
|
|
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.
|
|
<
< |
Write Access Restriction for a Whole TWiki Web
|
>
> |
Write Access Restriction by Web
|
|
You can define restrictions of who is allowed to make changes to a TWiki web. This includes creating new topics, changing topics or attaching files.
|
|
- DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in WebPreferences)
- ALLOWTOPICCHANGE (in topic) overrides ALLOWWEBCHANGE (in WebPreferences)
|
|
<
< |
Rename Access Restriction for Individual Topics
|
>
> |
Rename Access Restriction by Topic
|
|
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.
|
|
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.
|
|
<
< |
Rename Access Restriction for a Whole TWiki Web
|
>
> |
Rename Access Restriction by Web
|
|
You can define restrictions of who is allowed to do renames for a TWiki web.
|
|
- DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in WebPreferences)
- ALLOWTOPICRENAME (in topic) overrides ALLOWWEBRENAME (in WebPreferences)
|
|
<
< |
Read Access Restriction for a Whole TWiki Web
|
>
> |
Read Access Restriction by Web
|
|
You can define restrictions of who is allowed to view a TWiki web.
|
|
- Set DENYWEBVIEW = < list of users and groups >
- Set ALLOWWEBVIEW = < list of users and groups >
|
|
<
< |
Notes for read access restriction:
|
>
> |
Read Access Restriction Notes
|
|
- 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. TWiki Installation has more on basic authentication based on the
.htaccess file.
- There is a workaround if you prefer to to have unrestricted access to view topics located in normal webs, and to authenticate users only for webs where view restriction is enabled:
|
|
- It is not recommended to restrict view access to individual topics since all content is searchable within a web.
- The view restriction is not suitable for very sensitive content since there is a way to circumvent the read access restriction.
|
|
<
< |
-- PeterThoeny? - 16 Mar 2001
|
|
|
|
<
< |
NOTE:
|
>
> |
The SuperAdminGroup?
|
|
The above schema can lock completely a topic in case of a typing error of the ALLOWTOPICCHANGE setting (see UnchangeableTopicBug). To avoid this:
- set the
$superAdminGroup variable in TWiki.cfg to the name of a group of users that are always allowed to edit/view topics. E.g.:
|
|
- the default setting is not to have superusers
|
|
>
> |
- |
To hide access control settings from normal browser viewing, place them in comment markers.