In the archive Startup.Auth.cs
, add the options to configure them:
public void ConfigureAuth(IAppBuilder app)
{
// Enable the application to use a cookie to store information for the signed in user
app.UseCookieAuthentication(new CookieAuthenticationOptions
{
AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie,
LoginPath = new PathString("/Account/Login"),
ExpireTimeSpan = new System.TimeSpan(0,30,0),
SlidingExpiration = true
});
}
Just change the timing of the property ExpireTimeSpan
for a time which it deems appropriate.
Of documentation:
Expiretimespan:
Controls how Much time the cookie will remain Valid from the point it is created. The expiration information is in the protected cookie ticket. Because of that an expired cookie will be Ignored Even if it is passed to the server after the browser should have purged it
Slidingexpiration:
The Slidingexpiration is set to true to instruct the middleware to re-issue a new cookie with a new expiration time any time it processes a request which is more than Halfway through the expiration window.
What kind of requests? In development, ASP.NET MVC sends to your page a resource called Browser Link, that makes VS communicate with the generated page. That’s what we’re talking about?
– Leonel Sanches da Silva