Home/ Questions/Q 3985984
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T05:57:26+00:00

So my company has an ASP.NET web app, targeting .NET 3.5. I am tasked

  • 0

So my company has an ASP.NET web app, targeting .NET 3.5. I am tasked with building a ticketing system for them. I don’t really need to use any resources of the company app, except for authentication. I would like to target .NET 4.0 and use the 4.0 goodies like entity framework and mvc 3.0. If I create an application targeting .net 4 nested within the main web app in IIS, is there a way to persist authentication so they do not require a different session within the 4.0 web app?

Please let me know if I am being unclear.

Thank you.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you use membership authentication you can share sessions between different web applications provided the following is true:

    1. All of them share the same machine
      key – you can set the machineKey
      explicitly in each web.config to the
      same value.

    2. You are using the same
      authentication cookie name (i.e.
      .ASPXAUTH by default)

    There might be other ways, but this is how I got it to work.

    Also see this article for reference: Forms Authentication Across Applications

    • 0