I took a look at the code and is similar to that described in the Lift wiki [1].
IMHO - It shouldn't break the existing login but I wanted to try it out after Vladimir did his commit. It is easy to test - after the commit- try and login via username / password and / or openID. D. [1] http://www.assembla.com/wiki/show/liftweb/How_to_use_Container_Managed_Security On Mon, Mar 28, 2011 at 5:21 PM, Ethan Jewett <[email protected]> wrote: > Sounds good to me. I haven't been able to review the code yet, as > Vladimir requested, but actually the easiest way to get a review is > probably to commit it and then reply to the commit message requesting > that people take a look at it :-) > > One question: Is this going to break the existing login, or will it be > optional via a configuration parameter? > > Ethan > > On Mon, Mar 28, 2011 at 4:44 PM, Richard Hirsch <[email protected]> wrote: >> Vladimir has added an initial version of code for this issue ( >> https://issues.apache.org/jira/browse/ESME-214) . I'd like to move >> forward on this issue. >> >> My suggestion to get things going again: >> >> 1. Vladimir should commit his changes in Boot.scala + UserAuth.scala >> 2. Dick will test this in Tomcat. >> 3. We then document this functionality in two blogs - one for jetty >> and one for Tomcat >> >> Any thoughts? >> >> D. >> >
