urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Answer to Joey, and justify my text (in the source)

master
http://emptty.myopenid.com/ 2009-08-29 04:28:01 -04:00 committed by Joey Hess
parent 9f75d3b1f3
commit a4c9a8461c
1 changed files with 17 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
doc/todo/Restrict_page_viewing.mdwn
View File

@ -1,15 +1,27 @@
I'd like to have some pages of my wiki to be only viewable by some users.
I could use htaccess for that, but it would force the users to have 2 authentication mecanisms, so I'd prefer to use openID for that too.
I could use htaccess for that, but it would force the users to have
2 authentication mecanisms, so I'd prefer to use openID for that too.
* I'm thinking of adding a "show" parameter to the cgi script, thanks to a plugin similar to goto.
* When called, it would check the credential using the session stuff (that I don't understand yet). If not enough, it would serve a 403 error of course.
* If enough, it would read the file locally on the server side and return this as a content.
* I'm thinking of adding a "show" parameter to the cgi script, thanks
to a plugin similar to goto.
* When called, it would check the credential using the session stuff
(that I don't understand yet).
* If not enough, it would serve a 403 error of course.
* If enough, it would read the file locally on the server side and
return this as a content.
Then, I'd have to generate the private page the regular way with ikiwiki, and prevent apache from serving them with an appropriate and much more maintainable htaccess file.
Then, I'd have to generate the private page the regular way with ikiwiki,
and prevent apache from serving them with an appropriate and
much more maintainable htaccess file.
-- [[users/emptty]]
> While I'm sure a plugin could do this, it adds so much scalability cost
> and is so counter to ikiwiki's design.. Have you considered using the
> [[plugins/httpauth]] plugin to unify around htaccess auth? --[[Joey]]
>> I'm not speaking of rendering the pages on demand, but to serve them on demand.
>> They would still be compiled the regular way;
>> I'll have another look at [[plugins/httpauth]] but I really like the openID whole idea.
>> --[[emptty]]