如何在中间件中将用户对象绑定到请求

我正在用 Laravel Spark 1.0 (Laravel 5.2) 编写一个应用程序.我为代理(api)身份验证编写了一个自定义中间件.这是代码:

i'm writing an application in Laravel Spark 1.0 (Laravel 5.2). I wrote a custom middleware for agent (api) authentication. This is the code:

<?php

namespace AppHttpMiddleware;

use AppAgent;
use Closure;
use IlluminateHttpRequest;

class AgentAuth
{
    /**
     * Handle an incoming request.
     *
     * @param  IlluminateHttpRequest  $request
     * @param  Closure  $next
     * @return mixed
     */
    public function handle($request, Closure $next)
    {
        if( isset($request->token) &&  !empty($request->token) )
        {
            $agent = Agent::where('token', '=', $request->token)->first();

            if( $agent != NULL )
            {
                $team = $agent->Team()->first();
                $user = $team->User()->first();

                $request->merge(['team' => $team ]);
                $request->merge(['user' => $user ]);

                return $next($request);
            }
            else {
                return response('Unauthorized 2.', 401);
            }

        }
        else {
            return response('Unauthorized 1.', 401);
        }
    }
}

在默认的 Laravel 身份验证中,用户对象被注入到请求中(参见 Laravel 文档):https://laravel.com/docs/5.2/authentication#retrieving-the-authenticated-user

In the default laravel authentication the user object is injected in the request (see laravel docs): https://laravel.com/docs/5.2/authentication#retrieving-the-authenticated-user

因此您可以使用以下方法检索用户:

So you can retrieve the user using:

$request->user();

Spark 显然是用这个方法来检查用户订阅是否有效(laravelsparksrcHttpMiddlewareVerifyUserIsSubscribed):

Spark obviously use this method to check if user subscription is valid (laravelsparksrcHttpMiddlewareVerifyUserIsSubscribed):

if ($this->subscribed($request->user(), $subscription, $plan, func_num_args() === 2)) {
            return $next($request);
        }

而且它不起作用,因为使用我的中间件,您可以使用以下方法检索用户:$request->user; 但不能使用 Laravel 默认值 $request->user();

And it's not working because, with my middleware, you can retrieve the user using: $request->user; but not with the laravel defaults $request->user();

我应该如何将用户对象注入到请求中?

How should i inject the user object into the request?

提前致谢

服务提供者中的 Laravel (IlluminateAuthAuthServiceProvider@registerRequestRebindHandler)

Laravel in the service provider (IlluminateAuthAuthServiceProvider@registerRequestRebindHandler)

使用此代码将对象用户绑定到请求:

Use this code to bind object user to the request:

/**
     * Register a resolver for the authenticated user.
     *
     * @return void
     */
    protected function registerRequestRebindHandler()
    {
        $this->app->rebinding('request', function ($app, $request) {
            $request->setUserResolver(function ($guard = null) use ($app) {
                return call_user_func($app['auth']->userResolver(), $guard);
            });
        });
    }

我尝试在中间件中插入此代码并进行适当的更正,但我不知道如何使其工作.

I tried to insert this code, with the appropriate correction, in the middleware but i can't figure out how to make it work.

推荐答案

我没有 Spark 的副本来尝试这个 &确保我所做的对你来说是正确的,但我认为这会有所帮助:

I don't have a copy of Spark to try this & ensure what I'm doing is correct for you, but I think this will help:

1) 一个假设 - 我相信你是说是的,这条线会让你找到你想要的用户:

1) An assumption - I believe you are saying that yes, this line will get you the user you want:

$user = $team->User()->first();

并且您只想将其绑定到请求,以便您稍后可以通过以下方式在您的应用中访问此用户:

and you merely want to bind it to the request so that you can access this user later in your app via:

$request->user()

2) 如果这是真的,那么我所做的就是简化您提供的代码以添加:

2) If this is true, then all I did was simplify the code you provided to add:

$request->merge(['user' => $user ]);

//add this
$request->setUserResolver(function () use ($user) {
    return $user;
});

// if you dump() you can now see the $request has it
dump($request->user());

return $next($request);

我还在路由闭包中使用了 $request->user(),它就在那里.

I also $request->user() in the route closure, and it is there.

应用重新绑定对我来说有点奇怪,似乎没有必要.我不确定你正在做的事情是否真的需要这个.

The app rebinding was a little strange to me, and didn't seem necessary. I'm not sure that anything would really need this for what you are doing.

相关文章