The laravel database session with angularjs was not working , but It works in pure laravel project.

This Is my session.php file, while i using this code in my laravel(5.6) with angularjs project. i have loged in successfully, but data not loaded in webpage, and when the moment i refresh the page it will automatically logged out .

env(‘SESSION_DRIVER’, ‘database’),

/*
|————————————————————————–
| 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’ => env(‘SESSION_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 Database Connection
|————————————————————————–
|
| When using the “database” session driver, you may specify the database
| connection that should be used to manage your sessions. This should
| correspond to a connection in your “database” configuration file.
|
*/

‘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 Cache Store
|————————————————————————–
|
| While using one of the framework’s cache driven session backends you may
| list a cache store that should be used for these sessions. This value
| must match with one of the application’s configured cache “stores”.
|
*/

‘store’ => env(‘SESSION_STORE’, null),

/*
|————————————————————————–
| Session Lottery
|————————————————————————–
|
| Some session drivers require lottery style selection of the random values
| for the garbage collection routines. An example of this is the file
| session driver. Set a probability out of 100 for garbage collection.
|
*/

‘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’,
str_slug(env(‘APP_NAME’, ‘laravel’), ‘_’) . ‘_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’ => 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’ => null,

/*
|————————————————————————–
| 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,

/*
|————————————————————————–
| Same-Site Cookies
|————————————————————————–
|
| This option determines how your cookies behave when cross-site requests
| take place, and can be used to mitigate CSRF attacks. By default, we
| will set this value to “lax” since this is a secure default value.
|
| Supported: “lax”, “strict”, “none”, null
|
*/

‘same_site’ => ‘lax’,

];