Two different ASP.Net membership providers on one web solution

I created two websites, both of which use a custom membership provider, which I wrote myself.

One of these sites has long been online and working fine. Now I installed a different site on the same web server in the same Web as another application. I also gave a separate ApplicationPool for each solution.

If now the client logs on to one site, he loses the session on another and vice versa. It is not possible to log in to both sites together. Everything else works fine.

What is the relationship between these two sites. Do I need to change anything in my membership providers?

+1
asp.net-membership
source share
1 answer

Perhaps if you change the session cookie name for each application:

http://msdn.microsoft.com/en-us/library/h6bb9cz9

Update: The correct answer was to change the name of the form. See comments below.

+1
source share

Source: https://habr.com/ru/post/651223/


All Articles