R
Rich Williams
Hi All,
Hope i can explain my problem. I have a single webapp that uses ASP.NET 2.0
Membership . Inside my website setup in IIS i have created an domain alias
that will be secured. The webapp actually runs multiple domains and 1 SSL
domain.
I need to ensure that my users stay logged in when moving between the
secured pages and the insecured pages. Obviously these pages are under
different domains/aliases (ie: www.mystore.com & ssl.mystore.com) but again,
are the same "website" in IIS and the same application. I also need to pass
around things like shopping cart information etc. between the SSL domain
(alias) and the regular domains. Will the member information, status etc be
passed between the website aliases?
First of all will this work? How are the ASP.NET 2.0 Membership sessions
stored? Per webapp or per domain? What is the process of getting this type of
scenario working? I have searched many sources and have yet to find a
documented solution. Am i going about this the wrong way?
Hope i can explain my problem. I have a single webapp that uses ASP.NET 2.0
Membership . Inside my website setup in IIS i have created an domain alias
that will be secured. The webapp actually runs multiple domains and 1 SSL
domain.
I need to ensure that my users stay logged in when moving between the
secured pages and the insecured pages. Obviously these pages are under
different domains/aliases (ie: www.mystore.com & ssl.mystore.com) but again,
are the same "website" in IIS and the same application. I also need to pass
around things like shopping cart information etc. between the SSL domain
(alias) and the regular domains. Will the member information, status etc be
passed between the website aliases?
First of all will this work? How are the ASP.NET 2.0 Membership sessions
stored? Per webapp or per domain? What is the process of getting this type of
scenario working? I have searched many sources and have yet to find a
documented solution. Am i going about this the wrong way?