Mike Orr <[EMAIL PROTECTED]>: [...] > That sounds familiar too... > > In any case, when we figure it out we need to put it on the wiki as an > alternate authentication method.
Yeah. I would even go so far as to suggest perhaps a utility method or two... No real need to go through all this explicit header-passing and environment variable-parsing if you could just have a method that dealt with it... E.g. instead of having req.remoteUser() raise an exception if the user isn't log in, how about asking the user for a username and password? (This may not be the most appropriate place to put the code -- I don't know.) > > But there is no such standard for the password, IIRC. > > If you need the password, van you use database authentication and look up the > password in the database by the username? If I have a database authentication solution, I will no longer need the password. The problem is that I'm currently using a plain vanilla binary rpm installation of Apache, and would rather not mess around with compiling and installing modules unless I really have to. If I could solve this all in Webware, that would be preferrable. (Otherwise, mod_auth_pgsql sounds like a very good alternative.) Anyhow: Whether it be based on HTTP authentication, or a standard cgi/form/session solution, it seems to me that a fully encapsulated and extremely simple authentication mechanism would be useful in Webware. The example from the distribution is nice enough (and I've recoded it into a custom version), but not exactly dead simple; if I were a newbie trying to set up a password-protected PSP page, I would probably give up very quickly. -- Magnus Lie Hetland The Anygui Project http://hetland.org http://anygui.org _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
