[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 701
  • Last Modified:

Sharing session information across two web applications

We have two ASP.net web applications AppA and AppB under the same domain, is it possible to preserve session information from App A to App B ?  Users from AppA are redirected to AppB with information (login and other crtitical data) being transfered by query string to AppB. Now is it possible to maintain reliable distinct session for each user being transfered between the two applications ?

I noticed some user information was being mixed up with the others, is a query string not a good solution for this purpose ?
0
byte1
Asked:
byte1
  • 3
  • 2
1 Solution
 
informaniacCommented:
You could have a look @ storing the Session in a sql server d/b.
0
 
byte1Author Commented:
Yes, I am aware of that option, but would using the query string transfer method not create a unique session ?
0
 
informaniacCommented:
How are u sending the session information currently?

Response.Redirect("url"+SessionInfo) ?? something like this?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
byte1Author Commented:
yes, thats how i send information over to AppB.

What i am interested in knowing is under the same domain, is every call to AppB unique with a unique session id.
0
 
informaniacCommented:
If I'm not mistaken, if u r redirecting from appa to appb then the session id should remain the same
0
 
RamuncikasCommented:
Hello

As a matter of fact each ASP.NET application has it's own session navigating from AppA to AppB will create a new session on AppB while session on AppA will be still active. Even if SessionIDs on both applications are the same Sessions as instances are two different objects and there is no straight forward way to share info between them. If you come back to AppA from AppB before session expires on AppA you will use the same session object.

Sql Session state management is way to go, but you have to keep in mind to major cons:
 - Sql Session state management is about 30% slower then standard InProc Session state management
 - If you want to use Sql Session state management all objects stored in Session have to be serializable. That means there is no problem to store int, string and even datatable into session. But there is a problem to store custom class becuse and it should implement ISerializable interface

I would suggest you two solutions:
1. Do the same as you do now just take ALL query string, encrypt it and pass encryption result as a query string. Safer but not safe enough.
2. Use database to store/retrieve data to be passed among two applications. This might be slower then query string but safer for sure. And this will be even faster then managing Session state in Sql because Sql Session state management will query database many more times then you storing retrieving data on cross-application navigation

If you use Forms authentication in both of your applications you could also implement Single Sign-on (SSO).
http://www.codeproject.com/KB/web-security/aspnetsinglesignon.aspx
(there are many more articles, just ask google :) )
If additional info you want to have in both applications is user relevant then you could extend Users table and have that info stored/read from there.

HTH
R
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now