aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJon Dowland <jmtd@debian.org>2010-03-18 15:21:38 +0000
committerJon Dowland <jmtd@debian.org>2010-03-18 15:21:38 +0000
commitea07442e7ac6ef80cd98625b32f66bafc6af26b5 (patch)
tree8d1d8a706595b2e04d4d733ee949fd3a3d3b45e6 /doc
parenta02a06cb9dc0a82dd4028c9f4b506dcf899c9a41 (diff)
downloadikiwiki-ea07442e7ac6ef80cd98625b32f66bafc6af26b5.tar
ikiwiki-ea07442e7ac6ef80cd98625b32f66bafc6af26b5.tar.gz
comment
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/ACL.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/ACL.mdwn b/doc/todo/ACL.mdwn
index 57979385d..c1f5d86f0 100644
--- a/doc/todo/ACL.mdwn
+++ b/doc/todo/ACL.mdwn
@@ -21,6 +21,11 @@ something, that I think is very valuable.
>>>> Which would rule out openid, or other fun forms of auth. And routing all access
>>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]]
+>>>>> I think what Joey is suggesting is to use apache ACLs in conjunction
+>>>>> with basic HTTP auth to control read access, and ikiwiki can use the
+>>>>> information via the httpauth plugin for other ACLs (write, admin). But
+>>>>> yes, that would rule out non-httpauth mechanisms. -- [[Jon]]
+
Also see [[!debbug 443346]].
> Just a few quick thoughts about this: