en:user:authentication
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
en:user:authentication [2018/08/27 01:00] – kjdon | en:user:authentication [2018/08/27 01:54] – [Usage information] kjdon | ||
---|---|---|---|
Line 3: | Line 3: | ||
A special type of user called an " | A special type of user called an " | ||
+ | |||
<TABAREA tabs=" | <TABAREA tabs=" | ||
Line 17: | Line 18: | ||
<TAB> | <TAB> | ||
<!-- id:582 -->To access this facility, click the appropriate link on the front page. | <!-- 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. | <!-- id:583 -->The entry page gives information about each of the collections offered by the system. | ||
Line 33: | Line 36: | ||
- | ===== <!-- id:599 -->User management ===== | + | =====User management ===== |
- | <!-- id:600 -->Greenstone | + | Greenstone's user database |
- | access to certain facilities. This is used to restrict | + | |
- | who are allowed | + | |
- | Authentication is done by requesting a user name and password. | + | Authentication |
- | <!-- id:601 -->From the administration page users can be listed, | + | The current list of groups |
- | 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. | + | |
- | | + | |
- | collections and alter (and delete) existing ones. | + | |
- | <!-- id:602 -->When Greenstone is installed, there is one user called //admin// who belongs | + | |
- | to both groups. The password for this user is set during the installation process (If you | + | |
+ | * **<collection-name> | ||
+ | * **all-collections-editor**: | ||
+ | |||
+ | |||
+ | When Greenstone is installed, there is one user called //admin// who belongs | ||
+ | to both the administrator and all-collections-editor | ||
did not set a password during installation, | did not set a password during installation, | ||
username = //admin//, password = // | username = //admin//, password = // | ||
- | This user can create new names and passwords for users who belong just to the | ||
- | // | ||
- | to build collections. User information is recorded in two databases that are placed in | ||
- | the Greenstone file structure (see the // | ||
+ | For more details about user management, see the appropriate page for your Greenstone: | ||
+ | * [[en: | ||
+ | * [[en: | ||
===== Additional features ===== | ===== Additional features ===== | ||
Line 68: | Line 66: | ||
- | |||
- | |||
- | =====Usage information===== | ||
- | |||
- | You can enable usage logging by setting the logcgiargs option to true in greenstone/ | ||
- | |||
- | You can find out what the cgi arguments mean by going to the Administration page of your Greenstone installation, | ||
Line 82: | Line 73: | ||
* The [[http:// | * The [[http:// | ||
- | </ | ||
en/user/authentication.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1