Darren, I'm going to split out the auth part of ESME. There will a generic "auth data" table that will contain generic information for authentication schemes. Each scheme (and many schemes may be present simultaneously) will write a row in the table.
I'll write the openid plugin and you can write others. How does that sound? Thanks, David On Tue, Jan 6, 2009 at 10:51 AM, Darren Hague <[email protected]> wrote: > Quick notes from the 1st part of the Scrum call today (Dick to produce > notes from part 2). > > We need to look at auth approach, with JAAS preferred for J2EE > container-based authentication & authorisation. This will give easy access > to enterprise-based authentication systems. OpenID, while a good initial > choice, is causing usability and technical problems and is of little > relevance to the enterprise context. > > Daniel will look at removing the OpenID dependency from ESME (mostly by > asking David and the rest of the Lift community) > Darren will look at doing a JAAS/Lift sample app which cas serve as the > basis for JAAS auths in ESME, and of course can be contributed back to Lift. > > Cheers, > Darren -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us Follow me: http://twitter.com/dpp Git some: http://github.com/dpp
