Re: Session State across ASP.NET apps
From: Mark (maxmann_at_kc.rr.com)
Date: 06/01/04
- Next message: VB Programmer: "Re: I can't modify web.config"
- Previous message: Steve C. Orr [MVP, MCSD]: "Re: debugging asp.net application"
- In reply to: Cowboy: "Re: Session State across ASP.NET apps"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Jun 2004 11:34:24 -0500
Yeah, we are already using a central (single) state server for all web
servers in our farm, so I knew about the encrypt decrypt thing for that.
I'm just talking about sharing the session between apps. I'm aware of some
of the hacks you mentioned. I guess I'm just looking for a fairly clean
solution, but it doesn't look like that exists.
thanks .
"Cowboy" <NoSpamMgbworld@comcast.netNoSpamM> wrote in message
news:uCShkq9REHA.1348@TK2MSFTNGP12.phx.gbl...
> Set the encrypt and decrypt key to the same value in each web. Then, set
the
> authentication cookie name (forms auth) to the same name. This will
> authenticate the user once for any number of servers. NOTE: If you farm,
you
> will have to use the same Session Server for all machine (I have not
> personally tested this, however).
>
> For session variables, I have yet to have found a solution. Currently, we
> persist session vars in a SQL Server database with a timestamp (cleared
out
> 12 hours later). You can then grab the vars in the other app.
>
> I have a theory that placing the applications in the same pool in IIS
might
> allow sharing of session vars, but have not tested it. Another possibility
> is to set up a web service in each app to pass vars to the other app.
Since
> the web service would recognize the session ID, it could pass back the
info.
> NOTE: For high security, you would have to encrypt the data before
throwing
> into the web service return, as a sniffer could get session IDs and query
> your web service. I have not tested this yet, either.
>
> As for the article you link to, you can do what the article suggests
without
> the massive delete, edit the .webinfo file crap if you set up the parent
app
> and make the other "apps" subdirs of the parent app (importing, if child
> apps already completed). This is really a non-solution for most of us, as
> you are essentially killing the child apps and making a single parent app
> with all of your applications. You cannot set up the application on a
unique
> CName, like app1.mydomain.com, as it is tied to the other apps*. Yuck!
>
> * Actually, there is a way to kludge that too, but also not recommended.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ************************************************
> Think Outside the Box!
> ************************************************
>
> "Mark" <maxmann@kc.rr.com> wrote in message
> news:%23LxXX$0REHA.2404@TK2MSFTNGP09.phx.gbl...
> > Ok, I know that .net inherently does not share session data across
asp.net
> > projects, but is there any decent work around to this.
> > We already have a big chunk of our application using the asp.net session
> > object (using state service). I'd like to start breaking out
> > our functionality into component projects, but I'd like to get this
> session
> > issue worked out first.
> >
> > Any ideas??
> >
> > I found this article , but it sounds like kind of a pain.
> >
> > http://www.asp101.com/articles/jayram/sharestate/default.asp
> >
> >
> >
>
>
>
- Next message: VB Programmer: "Re: I can't modify web.config"
- Previous message: Steve C. Orr [MVP, MCSD]: "Re: debugging asp.net application"
- In reply to: Cowboy: "Re: Session State across ASP.NET apps"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
