From 6dccf4c67886a0212a871287379a8b6b887dfa6c Mon Sep 17 00:00:00 2001 From: Stefan Ritt Date: Thu, 20 Jan 2011 16:40:07 +0000 Subject: [PATCH] First version of Kerberos authentication SVN revision: 2373 --- doc/config.html | 190 +++++++++++++++++++++++++++--------------------- 1 file changed, 107 insertions(+), 83 deletions(-) diff --git a/doc/config.html b/doc/config.html index b697fed5..e6579944 100755 --- a/doc/config.html +++ b/doc/config.html @@ -1798,11 +1798,15 @@ Options Operating System = Linux{1}, Windows{2}

Multiple conditions -

It is possible to define conditions in more than one options list. The + + +

+ It is possible to define conditions in more than one options list. The only requiremnt is that conditions are uniquie, meaning that a condition in one option list cannot be used in another list. This can easily be avoided by using numbers for one condition and letters for the other condition, like in the following example: +

specifies for example the condition "Linux AND Main Building". If + +

+ specifies for example the condition "Linux AND Main Building". If several lines with condition combinations are true, the upper one is used. +

Conditions in the list display -

Conditional attributes are usually only used for change items + + +

+ Conditional attributes are usually only used for change items in the entry form. It might however be desirable to have conditional attibutes also working in the list display (the page where several entries are shown on a single page). The value of one attribute can then for example change which other attributes gets displayed via the list display option. To enable the evaluation of conditional attributes for the list display, on uses the option - +

+ It should be noted that this option can cause a significant performance + + +

+ It should be noted that this option can cause a significant performance degradation if many conditional attributes are defines, so it should only be turned on when it is really needed. +

+ + +
+
Access control
+

+ Note: Starting with version 2.9.0, the password level access using + the options Read password, Write password and + Admin password is not supported any more. Please use the user + level access as described below. +

+ +

+ Password file +

- -

-
-
- Access control -
-

- Reading and writing into logbooks can be constrained using two different - access methods, either with global passwords for read, write and admin - (config, delete), or with user- level passwords. Both methods can be - combined on the same server using different logbooks. For these two - schemes to work properly, cookies have to be turned on in your - browser. Please consult your browser documentation about how to do - that. -

- -

- These optional password statements define passwords for reading and - writing to the logbook, to delete entries in the logbook and to configure - a logbook via the Config menu. The passwords are stored in an - encoded form. To change them, use elogd directly with - the -r , -w and - -a flags. To set the write password of logbook - "linux" to "test", enter: -

- -

- The read password is queried by the browser with a pop-up window and - usually stays active for the entire browser session. The write and admin - passwords are stored in cookies on the browser side and expire after the - browser session. This time can be changed with the statement - Write Password Expiration = x or Admin - Password Expiration = x, where x is the expiration time - in hours. It should be noted that on some systems the daylight savings - time is calculated incorrectly, which can cause time offsets of one hour - between a server PC and a client PC. In this case one hour must be added - to the expiration time. If the expiration is set to "0", which is the - default, the passwords are kept for the current browser session only. - When the browser is restarted, the password must be re-entered. -

+ Access control is done on a user level with a password file. When a user + logs in, a session ID is created and placed as a "cookie" in the browser. + Using this cookie, the user can workin on the logbook until the cookie + expires. For this it is necessary that cookies are enabled in the browser. +

+ +

+ Following options can be used to control the behavior:

+

- An alternative to the read/write/admin passwords is the user level access - with a password file. This file contains user names and passwords in - XML format, such as + This file contains user names and passwords in XML format, such as