User Tools

Site Tools


en:user:authentication

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:user:authentication [2018/08/27 01:00] kjdonen:user:authentication [2023/03/13 01:46] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +
 +
 +
 ====== Authentication in Greenstone ====== ====== Authentication in Greenstone ======
 The Greenstone software comes equipped with an authentication system. Users can "Register" in the system, and can then access protected parts of the library, such as remote collection editing, online document editing (greenstone 3) and protected collections. The Greenstone software comes equipped with an authentication system. Users can "Register" in the system, and can then access protected parts of the library, such as remote collection editing, online document editing (greenstone 3) and protected collections.
Line 4: Line 7:
 A special type of user called an "administrator" is able to manage users. Anyone can register as a user, but only administrators can assign groups to that user. Groups control which collections/activities a user is allowed access to. A special type of user called an "administrator" is able to manage users. Anyone can register as a user, but only administrators can assign groups to that user. Groups control which collections/activities a user is allowed access to.
  
-<TABAREA tabs="Greenstone3,Greenstone2"> 
-<TAB> 
-To access this facility, click the **Login** button in the  
-upper right corner of the interface and enter your username and password (the default is "admin" 
-and "admin"). 
  
 For more information on security in Greenstone 3, refer to [[http://wiki.greenstone.org/doku.php?id=en:user_advanced:security|Security in Greenstone Collections]] For more information on security in Greenstone 3, refer to [[http://wiki.greenstone.org/doku.php?id=en:user_advanced:security|Security in Greenstone Collections]]
-</TAB> 
-<!-- #################################################################################################### 
-#################################################################################################### 
-################################################################################--> 
-<TAB> 
-<!-- id:582 -->To access this facility, click the appropriate link on the front page. 
  
-<!-- id:583 -->The entry page gives information about each of the collections offered by the system.  
-Note that //all// collections are included—for there may be “private” ones that do not appear on the  
-Greenstone home page. With each is given its short name, full name, whether it is publicly displayed, 
- and whether or not it is running. Clicking a particular collection's abbreviation brings up information about  
-that collection, gathered from its collection configuration file and from other internal 
- structures created for that collection. If the collection is both public and running,  
-clicking the collection's full name (the second link) takes you to the collection itself. 
  
-<!-- id:585 -->The administrative facility also presents configuration information about  
-the installation and allows it to be modified. It facilitates examination of the error  
-logs that record internal errors, and the user logs that record usage. It enables a  
-specified user (or users) to authorize others to build collections and add new material  
-to existing ones. 
  
  
-===== <!-- id:599 -->User management ===== 
  
-<!-- id:600 -->Greenstone incorporates an authentication scheme which can be used to control  +=====User management =====
-access to certain facilities. This is used to restrict the people  +
-who are allowed to access certain administration pages and allow for private collections/documents. +
  
-Authentication is done by requesting a user name and password.+Greenstone's user database is controlled by Administration Pages in the library. Admin users (users with the 'administrator' group set) can list users, edit their details (including which groups they belong to) and delete or create new ones. In addition, in greenstone 3, anyone can register themselves as new user (although an administrator needs to set their groups).
  
-<!-- id:601 -->From the administration page users can be listed, +Authentication of users is done by requesting a user name and password.
- new ones added, and old ones deleted.  +
-The ability to do this is of course also protected:  +
-only users who have administrative privileges can add new users. +
- It is also possible for each user to belong to different “groups”. +
- At present, the only extant groups are “administrator” and “colbuilder”.  +
-Members of the first group can add and remove users, and change their groups. +
- Members of the second can access the facilities described above to build new  +
-collections and alter (and delete) existing ones.+
  
-<!-- id:602 -->When Greenstone is installed, there is one user called //admin// who belongs  +The current list of predefined groups is as follows: 
-to both groups. The password for this user is set during the installation process (If you+ 
 +   ***administrator**: Gives permission to access and change site configuration and user accounts. 
 +   ***personal-collections-editor**: Gives permission to create new personal collections 
 +   * **<collection-name>-collection-editor**Gives permission to create and edit the "collection-name" collection, for example, reports-collection-editor. 
 +   * **all-collections-editor**: Gives permission to create new personal and global collections and edit all collections. Also gives permission to use the Collector (Greenstone 2). 
 + 
 +In addition, any custom group name can be used. 
 + 
 +When Greenstone is installed, there is one user called //admin// who belongs  
 +to both the administrator and all-collections-editor groups. The password for this user is set during the installation process (If you
 did not set a password during installation, the admin login will default to  did not set a password during installation, the admin login will default to 
 username = //admin//, password = //admin//).  username = //admin//, password = //admin//). 
-This user can create new names and passwords for users who belong just to the  
-//colbuilder// group, which is the recommended way of giving other users the ability  
-to build collections. User information is recorded in two databases that are placed in  
-the Greenstone file structure (see the //Greenstone Digital Library Developer's Guide//). 
  
 +For more details about user management, see the appropriate page for your Greenstone:
 +  * [[en:user_advanced:gs3_user_management|Greenstone 3 User Management]]
 +  * [[en:user_advanced:gs2_user_management|Greenstone 2 User Management]]
 +
 +===== Collection Security =====
 +
 +Collections can be made public or private. Additionally they can be password protected so that only users who belong to specified groups can access them. Or collections can be public with the exception of a few specified documents in that colleciton, which require a username and password to access.
 +
 +See the [[en:user_advanced:security|Security in Greenstone Collections]] page for more details about this.
  
 ===== Additional features ===== ===== Additional features =====
Line 68: Line 51:
  
  
- 
- 
-=====Usage information===== 
- 
-You can enable usage logging by setting the logcgiargs option to true in greenstone/etc/main.cfg. This saves a log in greenstone/etc/usage.txt. The log entry is basically a list of cgi arguments. One entry is generated for each page request to the library. 
- 
-You can find out what the cgi arguments mean by going to the Administration page of your Greenstone installation, or from [[en:urls| this page]]. 
  
  
Line 81: Line 57:
  
   * The [[http://www.nzdl.org/cgi-bin/library?a=p&amp;p=about&amp;c=authen-e|Formatting and Authentication]] demo collection uses authentication.   * The [[http://www.nzdl.org/cgi-bin/library?a=p&amp;p=about&amp;c=authen-e|Formatting and Authentication]] demo collection uses authentication.
- 
-</TAB></TABAREA> 
  
en/user/authentication.1535331600.txt.gz · Last modified: 2018/08/27 01:00 (external edit)