1 I'd like to have some pages of my wiki to be only viewable by some users.
3 I could use htaccess for that, but it would force the users to have
4 2 authentication mecanisms, so I'd prefer to use openID for that too.
6 * I'm thinking of adding a "show" parameter to the cgi script, thanks
7 to a plugin similar to goto.
8 * When called, it would check the credential using the session stuff
9 (that I don't understand yet).
10 * If not enough, it would serve a 403 error of course.
11 * If enough, it would read the file locally on the server side and
12 return this as a content.
14 Then, I'd have to generate the private page the regular way with ikiwiki,
15 and prevent apache from serving them with an appropriate and
16 much more maintainable htaccess file.
20 > While I'm sure a plugin could do this, it adds so much scalability cost
21 > and is so counter to ikiwiki's design.. Have you considered using the
22 > [[plugins/httpauth]] plugin to unify around htaccess auth? --[[Joey]]
24 >> I'm not speaking of rendering the pages on demand, but to serve them on demand.
25 >> They would still be compiled the regular way;
26 >> I'll have another look at [[plugins/httpauth]] but I really like the openID whole idea.
30 >>> [mod_auth_openid](http://trac.butterfat.net/public/mod_auth_openid), then?
31 >>> A plugin for ikiwiki to serve its own pages is far afield from ikiwiki's roots,
32 >>> as Joey pointed out, but might be a neat option to have anyway -- for unifying
33 >>> authentication across views and edits, for systems not otherwise running
34 >>> web servers, for systems with web servers you don't have access to, and
35 >>> doubtless for other purposes. Such a plugin would add quite a bit of flexibility,
36 >>> and in that sense (IMO, of course) it'd be in the spirit of ikiwiki. --[[schmonz]]
38 >>>> Yes, I think this could probably be used in combination with ikiwiki's
39 >>>> httpauth and openid plugins. --[[Joey]]