Question

I'm trying to set up TWiki on a server where I have to use cgiwrap. It's a known bug/fact that cgiwrap doesn't work with .htaccess unless the server's administration somehow sets it up (with one central .htpasswd). It was impossible/too hard of a task for the administration of the server, so now I'm in a situation where I would have to replace the relatively easy-to-use authentication provided by .htaccess to something else.

Since there are other TWiki sites running with cgiwrap, I'm sure this problem has been somehow solved by someone, but I just can't seem to find a solution. Somehow the scripts that need authentication should be forced to use some other authentication method. I am in no way an experienced perl programmer, so I'd rather just use some readymade library/script which would ask users for username and password when it's needed.

Another issue is TWiki's registration, which uses .htpasswd to store the usernames and passwords, so the alternative authentication method should preferably use it, too.

• TWiki version: 20020803beta
• Web server: Apache/1.3.20 (Unix)
• Server OS: Solaris 8
• Web browser: Doesn't have anything to do with this... (but I like to advertise it: Galeon 1.2.6)
• Client OS: Neither does this... (but I like to advertise it as well: Linux)

-- EetuHuisman - 29 Nov 2002

Answer

I have a local .htpasswd set up under TWiki, using suexec, which is similar to cgiwrap - see DreamhostSetupNotes for links. There is some info about cgiwrap setup with htpasswd but you may have tried that already - would require some admin work I think.

You might want to have a look at UserCookiePlugin, but that's probably not very secure and would still require some coding.

-- RichardDonkin - 02 Dec 2002