X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/91bb11721cceed3186cdf2de33d4aeae5114eb10..760c315589dc0e3fa0ba5380113f4e86a989a7d9:/doc/todo/ACL.mdwn?ds=inline diff --git a/doc/todo/ACL.mdwn b/doc/todo/ACL.mdwn index 827d4f6fa..cac6c9f18 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: @@ -32,7 +37,7 @@ Also see [[!debbug 443346]]. > defined in the wiki pages (although they could be). >* Given the previous two points, can't this be done with the `match_user()` > function defined by the [[plugins/attachment]] plugin (see the [[ikiwiki/pagespec/attachment]] pagespec info) -> and the [[plugins/lockedit]] plugin (see [[page_locking]])? +> and the [[plugins/lockedit]] plugin? > > For example, add the following to your config file: > @@ -41,6 +46,12 @@ Also see [[!debbug 443346]]. > would lock all pages unless you're john and editing a Discussion page. > It's a thought anyway :-). -- [[Will]] +>> Yes, writing per-user commit ACLs has become somewhat easier with recent +>> features. Breaking `match_user` out of attachment, and making the +>> lockedit plugin pass`user` and `ip` params when it calls `pagespec_match` +>> would be sufficient. And [[done]], configurable via +>> [[plugin/lockedit]]'s `locked_pages`. --[[Joey]] + I am considering giving this a try, implementing it as a module. Here is how I see it: @@ -63,3 +74,22 @@ Here is how I see it:
     \[[!acl user=* page=/subsite/* acl=/subsite/acl.mdwn]]
     
+ +Any idea when this is going to be finished? If you want, I am happy to beta test. + +> It's already done, though that is sorta hidden in the above. :-) +> Example of use to only allow two users to edit the tipjar page: +> locked_pages => 'tipjar and !(user(joey) or user(bob))', +> --[[Joey]] + +> > Thank you for the hint but I am being still confused (read: dense)... What I am trying to do is this: + +> > * No anonymous access. +> > * Logged in users can edit and create pages. +> > * Users can set who can edit their pages. +> > * Some pages are only viewable by admins. + +> > Is it possible? If so how?... + +>>> I don't believe this is currently possible. What is missing is the concept +>>> of page 'ownership'. -- [[Jon]]