On Mon, Aug 24, 2009 at 3:23 PM, Charles F. Munat <[email protected]> wrote:
> > I'm building two Lift applications that access the same back end > database -- one is for the public site, and the other, which will use a > subdomain, is for administration of the public site. > > A third application will access a separate database, but will be related > to the previous two sites. > > Any suggestions as to how I might have one login that keeps the user > logged in across all these sites? Obviously, OpenID would work, and > there's complex stuff involving LDAP servers, etc., but I'd like to keep > it fairly simple. > > Ideas? You could put a cookie at the top level for the domain that's an encrypted mix of the user's primary key and the current time. If the user comes to another one of the sites, it could examine the cookie and see if it should create a session for the user. > > > Thanks! > Chas. > > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
