php – Laravel 5.0 multiauth

路线和行动

Route::get('/asuser/{user}','AdminController@asuser')
        ->where('user','[0-9]+')
        ->name('asuser');
Route::get('/returnback','ClientController@returnback')
        ->name('returnback');

在管理员的控制器中：

public function asuser(User $client,Request $request) {
    /* insert checking if user has right either here with some field 
     * like $user->is_admin or using middleware settings and Policy
     */
    # who user is
    $fromId = Auth::user()->getId();

    # logging as a client
    Auth::login($client,true);

    # but keeping admin in a session
    $request->session()->put('adm_id',$fromId);

    return redirect()->route('some-client-route')
                    ->with('status','You are logged in as a client');
}

并返回ClientController

public function returnback(Request $request) {
    $fromId = Auth::user()->getId();

    # getting admin id
    $admId = $request->session()->pull('adm_id');
    $adminUser = User::find($admId);

    if (!$adminUser) {
        return redirect()->back()
                        ->with('status','Not allowed');
    }

    # logging out as a client and logging in as admin
    Auth::logout();
    Auth::login($adminUser,true);

    return redirect()->route('some-admin-route')
                    ->with('status','Welcome back!');
}

它准备好生产了吗？

不,这不对.这不是一个很好的解决方案,只是一瞥如何使用它.会话有生命周期,所以如果管理员在其生命周期中没有返回,session variables are lost并且他成为一个客户端(如果记住我= true,就像上面的代码一样).您可以将值存储在会话中但不存储在数据库列中.

此外,正如t1gor所提到的,您必须注意以下事实：当管理员是客户端时,您无法记录客户端的操作并发送事件.这是作为客户端登录的最严重问题.无论如何,我想,解决这个问题要比将所有auth逻辑移出视图更容易.

好吧,希望它有所帮助.