2010-06-11 04:45:14 +02:00
[[!tag wishlist]]
2010-06-14 20:14:43 +02:00
Ikiwiki is static, so access control for viewing the wiki must be
implemented on the web server side. Managing wiki users and access
together, we can currently
2010-06-11 04:45:14 +02:00
* use [[httpauth|plugins/httpauth/]], but some [[passwordauth|plugins/passwordauth]] functionnality [[is missing|todo/httpauth_feature_parity_with_passwordauth/]];
* use [[passwordauth|plugins/passwordauth]] plus [[an Apache `mod_perl` authentication mechanism|plugins/passwordauth/discussion/]], but this is Apache-centric and enabling `mod_perl` just for auth seems overkill.
2010-06-14 20:14:43 +02:00
Moreover, when ikiwiki is just a part of a wider web project, we may want
to use the same userdb for the other parts of this project.
2010-06-11 04:45:14 +02:00
2010-06-14 20:14:43 +02:00
I think an ikiwiki plugin which would (re)generate an htpasswd version of
the user/passwd base (better, two htpasswd files, one with only the wiki
admins and one with everyone) each time an user is added or modified would
solve this problem:
2010-06-11 04:45:14 +02:00
* access control can be managed from the web server
* user management is handled by the passwordauth plugin
* htpasswd format is understood by various servers (Apache, lighttpd, nginx, ...) and languages commonly used for web development (perl, python, ruby)
* htpasswd files can be mirrored on other machines when the web site is distributed
-- [[nil]]
2010-06-14 20:14:43 +02:00
> I think this is a good idea. Although unless the password hashes that
> are stored in the userdb are compatible with htpasswd hashes,
> the htpasswd hashes will need to be stored in the userdb too. Then
> any userdb change can just regenerate the htpasswd file, dumping out
> the right kind of hashes. --[[Joey]]
