Last post Jan 31, 2017 05:20 AM by Khuram.Shahzad
Jan 29, 2017 09:02 AM|Zain-Alabdin|LINK
I have a website which has subdomains such as ali.sarahah.com but if a user logs in from www.sarahah.com then goes to ali.sarahah.com the session is not saved. After searching I added the following in Startup.cs:
CookieDomain = ".sarahah.com"
I found out that .AspNetCore.Identity.Application cookie domain is still showing the subdomain and not the the domain and that session problem is still there.
Am I doing something wrong?
Jan 29, 2017 11:42 PM|bruce (sqlwork.com)|LINK
session is not related to authentication. it uses it own cookie. classic asp.net did not support sharing session with subsides, but depending on which session provider you are using in .net core you should be able to.
Jan 29, 2017 11:44 PM|Zain-Alabdin|LINK
Thanks for your reply,
I haven't changed the default session provider.
My main concern is, why don't the sessions stay the same or I'm not sure session is the correct word, I mean why don't user stay logged in on all subdomains.
Can you kindly help?
Jan 31, 2017 05:20 AM|Khuram.Shahzad|LINK
it shows subdomains not the domain because you allow the subdomains as ".sarahah.com" you can play with it by changing it,
Other part is it is possible to sign-in or sign-out a user from domain and all subdomain by using single sign on feature.