Indeed. I've grabbed the security code alone from OpenACS and got that working with AOLserver and PostgreSQL with just a few minor changes necessary (it about 20 of the .tcl files from OpenACS).
At the time OpenACS wouldn't install and I was unsure about taking on the whole OpenACS framework if I didn't need it What I've got is not very clean: there's probably buckets of unused procs and I'm sure quite a few files could be dropped completely if I spent some time further modifying the code. It was really an exercise to see how easy/hard it was to take OpenACS code and backport it to a vanilla AOLserver installation, but also partly driven by the need to find an extensive, well tested, performant, session management and security system. I'm more than happy to share what I've got with you (under all the normal GPL/MPL rules and regulations of course, since I didn't write the code of course), but can't spend a huge amount of time documenting it or whatever. Tim > -----Original Message----- > From: AOLserver Discussion [mailto:[EMAIL PROTECTED] Behalf > Of Brian Fenton > Sent: Tuesday, March 18, 2003 10:12 AM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] Best way for user authentication? > > > Jeremy, > Why re-invent the wheel? OpenACS already does this and much more and it's > all open source. Take a look at www.openacs.org for more code than you can > shake a stick at! > > Brian > > -----Original Message----- > From: Jeremy Cowgar [mailto:[EMAIL PROTECTED] > Sent: 15 March 2003 16:01 > To: [EMAIL PROTECTED] > Subject: [AOLSERVER] Best way for user authentication? > > Please forgive my ignorance, > > But can someone point me in a direction for user authentication with AOL > server? I understand two methods, but not certain how to make it all glue > together. > > The first method I know is http authentication which will pop up a dialog > box > and ask the user for their information. I would like to try to avoid this > because it's not quite as user friendly as having a login form. > > The second method is using cookies. I can handle this, but > ensuring that the > cookie is read for all .adp requests, that it is available in all my tcl > methods, in the included adp_ files, etc... that is confusing me a little. > > I am certian their are other ways as well. > > Can anyone give me a little info or point me to an information source on > this > subject? > > Thanks, > > Jeremy > > > > I. To remove yourself from this list: > > Send a message to "[EMAIL PROTECTED]" with the following text in > the BODY of your message: > > signoff aolserver > > II. For a complete list of listserv options please visit: > > http://listserv.aol.com/ > > III. For more AOLserver information please visit: > > http://www.aolserver.com/ > > > -- > AOLserver - http://www.aolserver.com/ > To Remove yourself from this list: http://www.aolserver.com/listserv.html > List information and options: http://listserv.aol.com/ > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
