tags:

views:

747

answers:

2

Hello

I have an ASP.NET app. I plan to run several instances of this app on the same server.

Each instance has its own domain, like www.app1.com and www.app2.com.

Each app instance has its own Admin area, that should be SSL protected. You can't install multiple SSL certs on the same machine and port number, so using https://www.app1.com/admin and https://www.app2.com/admin is a no-go.

I would then like to do the following:

Use my appname domain: www.appname.com with an SSL cert, and add an Application to that website in IIS for each client domain I have:

https://www.appname.com/app1/admin & https://www.appname.com/app2/admin.

But that would isolate session state between www.app1.com and https://www.appname.com/app1/admin - even though, they use the same Application Pool in IIS 7.

Is there a way to work around this?

+1  A: 

One way I've seen to share session state across different ASP.NET applications is to use one of the other options for storing session state information. Unfortunately I don't have access to IIS 7 at the moment, but assuming it is similar, here's how you configure it in IIS 6:

  • IIS Management Console
  • Bring up properties for the applicable virtual directory
  • ASP.NET tab -> Edit Configuration
  • State Management tab

The "Session state mode" defaults to InProc, but you can change it for your various application "instances" to use the same SQL Server database.

J c
A: 

You can use multiple SSL certificates on the same machine, they just need dedicated IP addresses.

Lucifer