This is a common problem seemingly with a variety of suggestions/solutions. I've read many previous topics and other sources but without success at my own problem.
Hosting a Laravel 6 app on Heroku. My session.php looks like:
<?php
return [
/*
|--------------------------------------------------------------------------
| Default Session Driver
|--------------------------------------------------------------------------
|
| This option controls the default session "driver" that will be used on
| requests. By default, we will use the lightweight native driver but
| you may specify any of the other wonderful drivers provided here.
|
| Supported: "file", "cookie", "database", "apc",
| "memcached", "redis", "array"
|
*/
'driver' => env('SESSION_DRIVER', 'file'),
/*
|--------------------------------------------------------------------------
| Session Lifetime
|--------------------------------------------------------------------------
|
| Here you may specify the number of minutes that you wish the session
| to be allowed to remain idle before it expires. If you want them
| to immediately expire on the browser closing, set that option.
|
*/
'lifetime' => 120,
'expire_on_close' => false,
/*
|--------------------------------------------------------------------------
| Session Encryption
|--------------------------------------------------------------------------
|
| This option allows you to easily specify that all of your session data
| should be encrypted before it is stored. All encryption will be run
| automatically by Laravel and you can use the Session like normal.
|
*/
'encrypt' => false,
/*
|--------------------------------------------------------------------------
| Session File Location
|--------------------------------------------------------------------------
|
| When using the native session driver, we need a location where session
| files may be stored. A default has been set for you but a different
| location may be specified. This is only needed for file sessions.
|
*/
'files' => storage_path('framework/sessions'),
/*
|--------------------------------------------------------------------------
| Session Database Connection
|--------------------------------------------------------------------------
|
| When using the "database" or "redis" session drivers, you may specify a
| connection that should be used to manage these sessions. This should
| correspond to a connection in your database configuration options.
|
*/
'connection' => env('SESSION_CONNECTION', null),
/*
|--------------------------------------------------------------------------
| Session Database Table
|--------------------------------------------------------------------------
|
| When using the "database" session driver, you may specify the table we
| should use to manage the sessions. Of course, a sensible default is
| provided for you; however, you are free to change this as needed.
|
*/
'table' => 'sessions',
/*
|--------------------------------------------------------------------------
| Session Sweeping Lottery
|--------------------------------------------------------------------------
|
| Some session drivers must manually sweep their storage location to get
| rid of old sessions from storage. Here are the chances that it will
| happen on a given request. By default, the odds are 2 out of 100.
|
*/
'lottery' => [2, 100],
/*
|--------------------------------------------------------------------------
| Session Cookie Name
|--------------------------------------------------------------------------
|
| Here you may change the name of the cookie used to identify a session
| instance by ID. The name specified here will get used every time a
| new session cookie is created by the framework for every driver.
|
*/
'cookie' => env('SESSION_COOKIE', 'my_app_session'),
/*
|--------------------------------------------------------------------------
| Session Cookie Path
|--------------------------------------------------------------------------
|
| The session cookie path determines the path for which the cookie will
| be regarded as available. Typically, this will be the root path of
| your application but you are free to change this when necessary.
|
*/
'path' => '/',
/*
|--------------------------------------------------------------------------
| Session Cookie Domain
|--------------------------------------------------------------------------
|
| Here you may change the domain of the cookie used to identify a session
| in your application. This will determine which domains the cookie is
| available to in your application. A sensible default has been set.
|
*/
'domain' => env('SESSION_DOMAIN', null),
/*
|--------------------------------------------------------------------------
| HTTPS Only Cookies
|--------------------------------------------------------------------------
|
| By setting this option to true, session cookies will only be sent back
| to the server if the browser has a HTTPS connection. This will keep
| the cookie from being sent to you if it can not be done securely.
|
*/
'secure' => env('SESSION_SECURE', false),
/*
|--------------------------------------------------------------------------
| HTTP Access Only
|--------------------------------------------------------------------------
|
| Setting this value to true will prevent JavaScript from accessing the
| value of the cookie and the cookie will only be accessible through
| the HTTP protocol. You are free to modify this option if needed.
|
*/
'http_only' => true,
];
I have SESSION_DRIVER=memcached, SESSION_SECURE=true, SESSION_DOMIN=my.heroku.host. Once logged in I have code that catches a 401 and asks user to log in again (click a button which logs them out in the backend and redirects to /login).
Multiple users are reporting that when they get this (presumably after 120 minutes per session.php), and log back in they immediately get asked to re-login again, as though their session has expired immediately. I've been able to replicate on Heroku, sometimes I get redirected, sometimes I seem to get the dreaded 'Page expired 419' Laravel page.
I have #csrf on my login form. And a <meta name="csrf-token" content="{{ csrf_token() }}"> at the top of each page once logged in. I am also sending X-CSRF-TOKEN as a header in each ajax request. Further, I'm not only detecting 401 but also 419 and attempting to refresh the csrf-token when that happens.
Once encountered, nothing seems to fix it, clearing cookies, cache etc. When I restart the Heroku dynos, however, everything works again. I've also been able to replicate locally (by reducing session lifetime) and the intercept, logout, login sequence works fine. So it's some kind of issue on Heroku/config. Any ideas welcome at this point!
I want to implement a "lock window" function into my application. Is it possible to lock a session and reactivate it?
Case: After x minutes the application will get locked. The user must now type in his password and will be redirected to the former route and logged in again.
In /config/session.php you can set the amount of idle time before the session expires:
/*
|--------------------------------------------------------------------------
| Session Lifetime
|--------------------------------------------------------------------------
|
| Here you may specify the number of minutes that you wish the session
| to be allowed to remain idle before it expires. If you want them
| to immediately expire on the browser closing, set that option.
|
*/
'lifetime' => 120, // edit this
If you want to include non idle time, you can create some middleware which can auto log-out your user. You can store the time the user logged-in in the session, and in the middleware store your $timeout variable. You can force log-out of an auth user like so:
auth()->logout()
if the time logged in + $timeout has passed.
I have this error Sorry, the page you are looking for could not be found. after close the project before logout and login before time expire please assist here is my session controller
'driver' => env('SESSION_DRIVER', 'file'),
/*
|--------------------------------------------------------------------------
| Session Lifetime
|--------------------------------------------------------------------------
|
| Here you may specify the number of minutes that you wish the session
| to be allowed to remain idle before it expires. If you want them
| to immediately expire on the browser closing, set that option.
|
*/
'lifetime' =>120,
'expire_on_close' =>true,
I have a wierd problem with my project. When user logs in to web application expiration time of laravel_session and XSRF-TOKEN are set at current timestamp.
Problem is that users randomly are logged out. I think that problems lies in session cookies and I don't know how to fix this problem.
Does someone knows where's the problem
Here is my session config:
'driver' => env('SESSION_DRIVER', 'file'),
/*
|--------------------------------------------------------------------------
| Session Lifetime
|--------------------------------------------------------------------------
|
| Here you may specify the number of minutes that you wish the session
| to be allowed to remain idle before it expires. If you want them
| to immediately expire on the browser closing, set that option.
|
*/
'lifetime' => 120,
'expire_on_close' => false
When user logged-in and remains inactive, How many seconds after that system logouts the user automatically? How to change this setting?
Assuming you are using the session driver to handle your authentication, you can change the time period for an idle session to expire in the /app/config/session.php file.
/*
|--------------------------------------------------------------------------
| Session Lifetime
|--------------------------------------------------------------------------
|
| Here you may specify the number of minutes that you wish the session
| to be allowed to remain idle before it expires. If you want them
| to immediately expire on the browser closing, set that option.
|
*/
'lifetime' => 120,
'expire_on_close' => false,