Tavis Rudd <[EMAIL PROTECTED]>: [snip] > > 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. > > I agree!! We talked about this back in Nov and put some notes on the > Wiki, but people got busy and the thread died out. > Here's the relevant URLs: > http://webware.colorstudy.net/twiki/bin/view/Webware/UserHandlingProj > http://webware.colorstudy.net/twiki/bin/view/Webware/WebwareUserManager
This looks great -- but perhaps a bit ambitious? I'm not saying the project should be scaled down, but that perhaps a more modest mechanism could be added as an initial step? (It might have a better chance of actually being implemented... :) Perhaps simply wrapping up the code from the example in the distribution in such a way that one could use/inherit it without knowing how it works? (To make this simple enough, one would perhaps have to drop the ID field stuff...) My hope was that HTTP auth could give me a ready-made, simple solution, when Webware didn't have one built-in... Even though I have one solution implemented, I generally like better to rely on standard solutions (maintained as part of the distribution) than to implement my own, when there is no obvious reason for me to do so. > Ng's authcookie extension to m2crypto sounds perfect for this sort of > stuff, but I have tested it yet. Sounds nice... (I guess this would require a separate installation of m2crypto...?) > Cheers > Tavis -- 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
