Authentication/Session cookie deleting after browser close
What are the exact steps required for a cookie to persist after a browser is closed? At the moment I have:
What are the exact steps required for a cookie to persist after a browser is closed? At the moment I have:
What is the difference between using AuthenticationManager SignIn as opposed to using SignInManager PasswordSignIn/SignIn? I have an implementation using the SignInManager and have my cookie expiration set to 30 days however it seems my web app will randomly expire my cookies far before 30 days. Would using the SignInManager implementation be the cause of this? Should I be using the AuthenticationManager implementation instead?
I made some changes to the testbed page, so I could make my question clearer here.
This is an interview question asked a month ago….
I am trying to to set up the login control to remember the login credentials of a user who has previously entered their user name and password successfully. I set the remember me property to true, but it doesnt seem to triger any events where I could read the cookie and auto login the user.
I’m using ASP.NET Session State to keep track of logged in users on my site.
I have a web app can be installed on lots of domains and paths.
I need help figuring out why my authentication ticket is expiring after about an hour on my hosted website. But if I run the site locally the authentication ticket stays alive for the correct amount of time.
I am using cookies authentication in my .net core mvc application. One of the requirements I have is to logout user when the browser is closed. I have set sliding expiration to 5 minutes in app. As expected if the user comes back to the website after 5 minutes user is redirected to login page, but if the user comes back inside 5 minutes the user is logged in automatically. Is there a way to logout user if the browser is closed?
Needing to update IIS web.config to secure cookies by adding SSL.