Let me see if I can summarize how we handled this... The common login system runs under its own application and handles user authentication then provides a list of applications the authenticated user has access to.
We link to the child application and the first item in the child application is a check for a session var that indicates an authenticated user. This is a session var that is uniquely named and only used in the login application system. We then set the userID to a local var, start the new cfapplication then run a custom tag that populates a new session variable (in our case a structure) of all the current users data. This approach does cause 1 more DB hit, but does allow the end applications to be independent of the login/authentication system. I'm leaving out some workarounds we created for cfapplicationless applications, and other finessing, but you get the general idea. The basic approach was to create a custom tag that can be called by any application to query the users authentication status and information. Hope that at least begins to shed some light on a different way to approach this. Trey Rouse Internet Project Supervisor Rice University > -----Original Message----- > From: Shawn Grover [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 24, 2002 5:46 PM > To: CF-Talk > Subject: RE: Urgent - Muliple CF Applications with common sessions? > > Thanks Shawn. We were hoping to avoid a database hit on every page. > I think our best solution is to use ONE application.cfm file, and > structures > to keep our variable names separate from each other. > Somthing like App1.Username, App2., App3.User - the use of the structures > will avoid variables with common names. > > Such is life.... > > Shawn Grover > > -----Original Message----- > From: Shawn Regan [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 24, 2002 4:34 PM > To: CF-Talk > Subject: RE: Urgent - Muliple CF Applications with common sessions? > > > One way I have heard of it done is to store the common session vars in a > database, which all the applications can access. > > HTH > > Shawn Regan > pacifictechnologysolutions > 15530-B Rockfield Blvd. Suite 4 > Irvine, CA 92618 > 949.830.1623 > w w w . p t s 1 . c o m > > > > -----Original Message----- > From: Shawn Grover [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 24, 2002 3:19 PM > To: CF-Talk > Subject: Urgent - Muliple CF Applications with common sessions? > > > My appologies if this is a double post, but I've yet to see the email > posted > back to me (therefore, I'm not sure if anyone else has seen it, even > though > it is in the archives). > > > We have built a common logon system for a few of our applications. This > > logon system sets some session variables, but these vars don't appear to > > be available in the other applications. > > > > Each application has it's own directory below wwwroot and it's own > > application.cfm file with the CFApplication tag. Each CFApplication tag > > specifies a different application name. Is this the cause of the > session > > variable problem? (i.e. application A sets a session variable, but > > application B cannot see it.) If so, how has anyone else handled this? > > The easiest ways I can think of are to create a common application.cfm > > file which includes a file from each application to setup their > > environment. Either that, or get creative with CFHTTP and post form > data > > to a "setVars.cfm" page in each application which would setup their > > session variables. Can't really think of any other way around the > > problem. > > > > Thanks for any input. > > > > Shawn Grover > > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
