[CWB] [ cwb-Feature Requests-2806330 ] CQPweb: More transparent username admin

SourceForge.net noreply at sourceforge.net
Wed Nov 11 21:39:48 CET 2009


Feature Requests item #2806330, was opened at 2009-06-14 23:28
Message generated for change (Settings changed) made by andrewhardie
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=722306&aid=2806330&group_id=131809

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: CQPweb
Group: None
>Status: Closed
Priority: 5
Private: No
Submitted By: Andrew Hardie (andrewhardie)
Assigned to: Andrew Hardie (andrewhardie)
Summary: CQPweb: More transparent username admin

Initial Comment:
(a) add documentation explaining CQPweb's use of Apache usernames for people who aren't Andrew
(b) add a "use internal apache functions" setting which can be on or off, so that the admin functions requiring Apache can be hidden for sysadmins who aren't using it.
(this should prob be a Boolean in config.inc.php, created by the autoconfig script)

The additional documentation should contain at least the following info:

 OK, the way it works is this. CQPweb
gets the username from the HTTP request (PHP variable
$_SERVER['REMOTE_USER'] ). User entries in the database are created 
automatically when they change their settings (or with default settings
when any script queries a user setting before they have been set.)
So, any username system that results in the username being part of the 
HTTP request will work fine in CQPweb: you just won't be able to use 
the admin control panel to create new usernames / groups because they
assume the use of an apache htpasswd utility and apache-style htpasswd
and htgroups files.

As far as I am aware this is exactly what BNCweb does. CQPweb puts 
each corpus in a separate folder in its root web-directory, so that
you can set access rights for each corpus separately, if you wish.
The internal apache-based functions do this with a .htaccess file in 
each folder.





----------------------------------------------------------------------

>Comment By: Andrew Hardie (andrewhardie)
Date: 2009-11-11 20:39

Message:
Both documentation and "hide apache" now complete. The variable
$cqpweb_uses_apache is set by default to true, but this can be overridden
in the config file.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=722306&aid=2806330&group_id=131809


More information about the CWB mailing list