Andy Taylor wrote:
Try the CGI::Application and CGI::Session mix, it works wonders for me. I've built a number of web apps that way with elaborate authentication schemes and these two modules were the only ones I ever required to complete the task (well excluding the obvious CGI and DBI modules :). To make life simpler for me I've built a third module that uses the facilities of the two modules mentioned above allowing me to build new apps with session management and authentication built in.I've been reading posts to this list for quite a while and appreciate all the helpful discourse. I'm about to start a fairly large project I think cgi::app will be good for but the authentication part is proving a stumbling block. The advice of Jesse and others to leave the authentication and authorization parts to the server - separated from the main code make much sense to me. That said, I don't have the option of installing mod_perl...the server my project will run on is used by many others and it can't afford the memory hit as well as the security issues that come with the shared environment. What I wanted to ask the list is....have any of you had success using cgi:app with some of the smaller more specific authentication/authorization apache modules like mod_auth_mysql etc. that don't require mod_perl. I envision having one separate module for logging in, another for changing passwords/user info, and then the main application broken down into several cgi:app's that don't contain any auth code.
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.