blocks|key|2888268|text|您应该做的是打开app/Http/routes.php|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2888269|并将您现有的所有路由包装为：|2888270|Route::group(['middleware'+=>+['web']],+function+()+{
++++//+here+your+previous+routes
});|code-block|syntax|javascript|2888271|编辑|BOLD|2888272|在测试之后，我可以确认这个行为。|2888273|在这些情况下：|2888274|2888275|5.1.17+->+5.2|unordered-list-item|2888276|5.1.23+->+5.2|2888277|5.1.28+->+5.2.*|2888278|2888279|升级到5.2版本后，用户似乎不再登录。当进入5.1分支的版本时，用户会保持登录状态。当从5.2返回到5.1时，将再次记录用户。|2888280|目前，您可能应该在此处创建问题https://github.com/laravel/framework/issues并等待响应|2888281|EDIT2|2888282|这似乎是官方和预期的行为，因为已经添加了升级指南：|2888283|2888284|由于身份验证系统的更改，当您升级到Laravel+5.2时，任何现有会话都将失效。|blockquote|2888285|2888286|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/laravel/framework/issues^0|8|J|0|0|0|0|2|0|0|0|0|0|0|0|0|0|F|17|0|0|0|5|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1R|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1S|8|@$9|1T|A|1U|B|O]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1V|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1W|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1X|8|@]|D|@]|E|$]]|$1|U|3|V|5|W|7|1Y|8|@]|D|@]|E|$]]|$1|X|3|Y|5|W|7|1Z|8|@]|D|@]|E|$]]|$1|Z|3|10|5|W|7|20|8|@]|D|@]|E|$]]|$1|11|3|-4|5|6|7|21|8|@]|D|@]|E|$]]|$1|12|3|13|5|6|7|22|8|@]|D|@]|E|$]]|$1|14|3|15|5|6|7|23|8|@]|D|@$9|24|A|25|1|26]]|E|$]]|$1|16|3|17|5|6|7|27|8|@$9|28|A|29|B|O]]|D|@]|E|$]]|$1|18|3|19|5|6|7|2A|8|@]|D|@]|E|$]]|$1|1A|3|-4|5|6|7|2B|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|1D|7|2C|8|@]|D|@]|E|$]]|$1|1E|3|-4|5|6|7|2D|8|@]|D|@]|E|$]]|$1|1F|3|-4|5|6|7|2E|8|@]|D|@]|E|$]]]|1G|$1H|$5|1I|1J|1K|E|$1L|1M]]]]

That you should do is open <code>app/Http/routes.php</code>

and wrap all your existing routes with:

<pre><code>Route::group(['middleware' =&gt; ['web']], function () {
 // here your previous routes
});
</code></pre>

EDIT

After testing I can confirm this behaviour. 

In those cases:

<ul>
<li>5.1.17 -> 5.2</li>
<li>5.1.23 -> 5.2</li>
<li>5.1.28 -> 5.2.*</li>
</ul>

after upgrade to 5.2 User seems not be logged anymore. When going in versions in 5.1 branch user stays logged. When going back from 5.2 to 5.1 user is logged again.

At the moment you should probably create issue here <a href="https://github.com/laravel/framework/issues" rel="nofollow">https://github.com/laravel/framework/issues</a> and wait for response

EDIT2

It seems it's official and expected behaviour because to upgrade guide has been added:

<blockquote>
 Because of changes to the authentication system, any existing sessions will be invalidated when you upgrade to Laravel 5.2.
</blockquote>

blocks|key|123558|text|我找出了导致会话无效的原因。问题出在会话保护的getName()方法上。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|123559|在5.1.17中：|123560|return+'login_'.md5(get_class($this));|code-block|syntax|javascript|123561|在5.2中(默认情况下$this->name为web+)：|123562|return+'login_'.$this->name.'_'.sha1(get_class($this));|123563|此外，类名本身也从Guard更改为SessionGuard|123564|如果我将此方法替换为：|123565|return+'login_'.md5('Illuminate\Auth\Guard');|123566|可以让我的会话保持登录状态。|123567|这是一个进步，但还不是一个完整的解决方案。真正的解决方案是使用新名称更新所有现有会话。我将编写一个脚本来完成此操作，然后更新我的答案。|123568|entityMap^0|N|9|0|0|0|B|B|N|3|0|0|9|5|H|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1C|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1I|8|@]|D|@]|E|$]]|$1|U|3|V|5|J|7|1J|8|@]|D|@]|E|$K|L]]|$1|W|3|X|5|6|7|1K|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1L|8|@]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|11|$]]

I figured out what is causing the session to be invalidated. The problem is the session guard's <code>getName()</code> method.

In 5.1.17:

<pre class="lang-php prettyprint-override"><code>return 'login_'.md5(get_class($this));
</code></pre>

In 5.2 (<code>$this-&gt;name</code> would be <code>web</code> by default):

<pre class="lang-php prettyprint-override"><code>return 'login_'.$this-&gt;name.'_'.sha1(get_class($this));
</code></pre>

Also, the class name itself changes from <code>Guard</code> to <code>SessionGuard</code>

If I replace this method with:

<pre class="lang-php prettyprint-override"><code>return 'login_'.md5('Illuminate\Auth\Guard');
</code></pre>

That keeps my sessions logged in.

This is progress but not a complete solution yet. The real solution is to update all of your existing sessions with the new name. I'll work on a script to complete this and then update my answer.

Upgrading from Laravel 5.1.17 to 5.2. My <code>config/auth.php</code> originally contained:

<pre class="lang-php prettyprint-override"><code>'driver' =&gt; 'eloquent',
'model' =&gt; 'Project\User',
'table' =&gt; 'users',
</code></pre>

New file is the same as the default, except with the updated namespace.

<pre class="lang-php prettyprint-override"><code>'defaults' =&gt; [
 'guard' =&gt; 'web',
 'passwords' =&gt; 'users',
],
'guards' =&gt; [
 'web' =&gt; [
 'driver' =&gt; 'session',
 'provider' =&gt; 'users',
 ],
 'api' =&gt; [
 'driver' =&gt; 'token',
 'provider' =&gt; 'users',
 ],
],
'providers' =&gt; [
 'users' =&gt; [
 'driver' =&gt; 'eloquent',
 'model' =&gt; Project\User::class,
 ],
],
</code></pre>

My env <code>SESSION_DRIVER</code> is <code>redis</code>. I did not clear anything from Redis. (Note, this also happened in my other projects where driver was <code>file</code>, but I didn't care about it as much for them.)

I have two branches, L5.2 and master (which is on 5.1.17). After switching branches, I simply run <code>composer install</code>

<blockquote>
 If I login on master, then switch to L5.2, I am logged out 
 If I switch back to master, I am logged back in 
 If I login on L5.2, then switch to master, I stay logged in 
 If I switch back to L5.2, I stay logged in
</blockquote>

I'm hesitant to upgrade if it's going to invalidate all of my users' sessions and force them to login again. Is there a way to avoid this?

The only other files that were modified were <code>composer.json</code>, <code>composer.lock</code>, <code>app/Exceptions/Handler.php</code>, and <code>config/app.php</code>; nothing that touched Auth.

Upgrading to Laravel 5.2 invalidates all sessions

身份验证

路由

Redis

从Laravel 5.1.17升级到5.2。我的config/auth.php最初包含：'driver' => 'eloquent','model'  => 'Project\User','table'  => 'users',新文件与默认文件相同，但具有更新的名称空间。'defaults' => [    'guar...

问升级到Laravel 5.2会使所有会话失效
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问升级到Laravel 5.2会使所有会话失效EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问升级到Laravel 5.2会使所有会话失效
EN