01.12.2012 Views

7 Components: the Function Pages - Developers

7 Components: the Function Pages - Developers

7 Components: the Function Pages - Developers

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The easiest way to add a new group is by filling out <strong>the</strong> form on <strong>the</strong><br />

TWikiGroups page. Here, you just have to enter a fitting name.<br />

Make sure that <strong>the</strong> name ends with “Group.” A new page is generated<br />

that already contains all of <strong>the</strong> elements <strong>the</strong> group needs. Importantly,<br />

you are already listed as a registered user in <strong>the</strong> GROUP variable.<br />

You will also see a second variable here, ALLOWTOPICCHANGE.<br />

This determines who can modify entries on a page. Admittedly, it<br />

would be ra<strong>the</strong>r ridiculous to limit certain actions to <strong>the</strong> Admin<br />

Group while at <strong>the</strong> same time allowing everyone <strong>the</strong> opportunity to<br />

make <strong>the</strong>mselves admins.<br />

This brings us to <strong>the</strong> access authorizations. There are two ways to<br />

define <strong>the</strong>m. Ei<strong>the</strong>r you explicitly define who may not execute an<br />

action, which makes it accessible to all <strong>the</strong> rest. This is an open security<br />

strategy with which you can exclude certain persons who, for<br />

example, have become conspicuous due to vandalism. The o<strong>the</strong>r<br />

method is to indicate who may execute certain actions. This is useful<br />

in actions critical to security, where you would like <strong>the</strong> circle of authorized<br />

persons is to be known by name. The two key words are<br />

“DENY” for <strong>the</strong> exclusive strategy and “ALLOW” for <strong>the</strong> inclusive<br />

approach.<br />

The two most frequent limitations relate to changing and renaming<br />

topics. The corresponding variables are:<br />

···*·Set ALLOWTOPICCHANGE = User, Groups<br />

···*·Set DENYTOPICCHANGE = User, Groups<br />

···*·Set ALLOWTOPICRENAME = User, Groups<br />

···*·Set DENYTOPICRENAME = User, Groups<br />

Of course, you only have to make <strong>the</strong> entries that you need. If you<br />

only wish to enable inclusive access, you do not need to make any<br />

DENY entries. The first two variables relate to <strong>the</strong> editing of a topic<br />

and also include <strong>the</strong> option of attaching files. Thus, users prohibited<br />

from editing a topic may also not upload anything to that topic. The<br />

second pair of variables relates to renaming or moving a topic.<br />

If you do not want to make it possible for everyone to immediately<br />

see who has access to a page and who does not, you can place<br />

<strong>the</strong> settings in HTML comments that begin in <strong>the</strong> line above <strong>the</strong><br />

variable settings and end in <strong>the</strong> line below it. By doing this, you<br />

won't prevent users experienced in HTML source text from reading<br />

and never<strong>the</strong>less finding out this information. However, it is also a<br />

question of aes<strong>the</strong>tics to refrain from making such technical information<br />

immediately obvious to everyone in normal browser viewing.<br />

Creating new<br />

groups<br />

Allow vs. deny<br />

Protecting<br />

individual pages<br />

Hiding access<br />

variables<br />

14.4 Access Control �<br />

�<br />

�<br />

209

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!