CODEWITHSUNDEEP
asp.netsessionauthentication
Dave Mackey
Dave Mackey

Reputation: 4432

Separate ASP.NET Applications, Shared Sessions?

I am working on a few applications. I like to keep my applications small, but I'd like to make it so that users that utilize more than one of these programs don't need to login to each application - it would remember and share session info. across the applications. Any thoughts on how I could accomplish this? Here are some examples of the separate applications I have / am working on:

I'd also have a dashboard application that would provide centralized insight into one's responsibilities and point one to applications that needed to be "processed" (e.g. "You haven't signed up for a room" or "You haven't filed x paperwork")

Upvotes: 0

Views: 178

Answers (1)

Cahit
Cahit

Reputation: 2534

If these are all under the same domain (e.g., http://server/app1 and http://server/app2, http://server/app3 etc.) then you can use a cookie that's set to be valid at the root level.

If not, then you need to adopt a single sign-on concept where the user is redirected to a central authority or login page that applies to all resources every time there's a need to authenticate.

Upvotes: 1

Related Questions