> In addition, it would not be hard to write your own Auth* module. Using > Apache and mod_perl, you could write a simple Auth handler which implements > all the functionality of mod_auth_pg, with ease. The mod_auth_pg.c code is > about 500 lines. Based on the functionality, I would bet you could replace > all that functionality in about 100-200 lines of Perl code. (It is a *very* > simple module!)
For those interested, the Eagle book describes pretty much exactly how to do this. (In C, IIRC, but it was easily translated, again, IIRC). > I'm not trying to talk you out of using mod_auth_pg! I just want to make > sure that everybody understands that what mod_auth_pg is doing is exactly > what mod_perl is intended to allow you to do in Perl. Naturally, C code The advantage to mod_auth_pg (or mod_auth_mysql, which is what I'm currently using) is that you can move it to environments where you don't have mod_perl. (such as a legacy box running mod_php3 [ick], which only coexists peacefully with mod_perl if you have sacrificed two goats and a Mac user). mod_auth_mysql doesn't allow Where clauses, which I'll have to look into -- my greatest problems are: -Having a login go across the site, currently it only propogates down the same directory tree -Logging out to login as someone else Since my agency is (finally) switching over to LDAP, I'll probably be cracking out the Eagle book to write my own authentication module soon, so I've found this discussion very useful. --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/cgiapp@lists.vm.com/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
