Thanks for the quick reply. I think it points me in the right (ie. different than what I was thinking) direction. I don't have an authentication server (yet), so my apps would all be under Glassfish or Jetty on the same server. So I'm off to read about JSESSIONID with these containers now.
Rog On Jan 28, 3:09 pm, David Pollak <feeder.of.the.be...@gmail.com> wrote: > On Thu, Jan 28, 2010 at 11:45 AM, Rogelio <rogbo...@gmail.com> wrote: > > Hello, > > > Admitted Scala and Lift newbie here. I've been searching and reading > > (Lift book and this newsgroup about 10 times day :-) about how to do > > this for over a month and have yet to find an answer (or at least one > > that I recognized :-) This list seems very friendly to us newbies, so > > here goes. > > > I'm wanting to create a web portal for use at work. On the main page > > the user will login and from there (based on user roles) the user can > > access other web applications running on the same or different servers > > but within the same domain. > > > So user goes to:https://portal.mycompany.comand logs in. From there > > the user can go to: > > > portal.mycompany.com\app1 > > portal.mycompany.com\app2 > > > or maybe/additionally > > > app3.mycompany.com > > app4.mycompany.com > > > If the user tried to go to app1-4 directly (without having logged in), > > they are directed to the main portal page to login first. > > > So, I know I need some sort of session data that app1-4 code can > > reference to see if the user is logged in. I have tried this in Rails > > (that's my web dev background) and just need to add this to the config > > file to have separate apps be able to access the session data for the > > domain a a whole: > > > ActionController::Base.session = { > > :domain => '.mycompany.com' > > } > > > Question is -- how to do this with Lift? I would like to ask for some > > actual code if I may -- 1) because I'm a newbie and 2) I suspect that > > the answer may be because Lift uses the container's session support > > (Glassfish, Jetty, etc) which I'm still trying to understand the > > underlying link between them and Lift. > > If all the apps are sharing the same app server then it's up to your > container to set the JSESSIONID cookie correctly for all the subdomains. > > If you have an authentication server and each of the different URLs is in > its own container, then you'll have to use a mechanism similar to the one > used in ProtoExtendedSession to share a cookie across the different app > servers and look up the user based on the cookie. > > Does this help? > > > > > > > Thanks in advance for the help. > > > Rog > > > -- > > You received this message because you are subscribed to the Google Groups > > "Lift" group. > > To post to this group, send email to lift...@googlegroups.com. > > To unsubscribe from this group, send email to > > liftweb+unsubscr...@googlegroups.com<liftweb%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/liftweb?hl=en. > > -- > Lift, the simply functional web frameworkhttp://liftweb.net > Beginning Scalahttp://www.apress.com/book/view/1430219890 > Follow me:http://twitter.com/dpp > Surf the harmonics -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
