Sentry

[ryanhungate]

Are there any issues with the auth class if using the cartalyst/sentry package for users? I had to override the constructor to place the user into the auth shield to make that work.

[philsturgeon]

If you get it working let me know. I'll need to integrate Sentry within the next few days.

[GrahamCampbell]

Sounds great guys!

[ryanhungate]

Well, i know that this is certainly not the desired way to tackle this, but I threw something together really fast that seemed to work, because im using Sentry. Its kind of a 3 pronged attempt here.

1. add the custom authenticators.
2. add the authenticator class
3. override the main controller and use sentry to set the user if they are currently logged in.

Doing only the authentication method where your returning the ID was not working, so I had to shove it into the controller as well, but again, im sure that this is not the official way to do it. Duct tape at best.

//Add to the custom auth config.
return array(
    'auth' => array(
        'basic' => function($app)
            {
                return new Dingo\Api\Auth\BasicProvider($app['auth']);
            },
        'logged_in_user' => function($app)
            {
                return new LoggedInAuthenticator;
            },
        'api_key' => function($app)
            {
                return new ApiKeyAuthenticator;
            }
    ),
);

//add the logged in authenticator.

use Illuminate\Http\Request;
use Illuminate\Routing\Route;
use Symfony\Component\HttpKernel\Exception\UnauthorizedHttpException;

class LoggedInAuthenticator extends \Dingo\Api\Auth\Provider
{
    public function authenticate(Request $request, Route $route)
    {
        if(($user = \Sentry::getUser())) {
            return $user->getId();
        }
        // Logic to authenticate the user for the given request. If it fails...
        throw new UnauthorizedHttpException(null, 'Your username or password is incorrect.');
    }
}

use Illuminate\Http\Request;
use Illuminate\Routing\Route;
use Symfony\Component\HttpKernel\Exception\UnauthorizedHttpException;

class ApiKeyAuthenticator extends \Dingo\Api\Auth\Provider
{
    public function authenticate(Request $request, Route $route)
    {
        if (($api_key = $request->input('api_key', false))) {
            if (($user = \User::fromApiKey($api_key, 'public'))) {
                return $user->getId();
            }
        } elseif(($user = \Sentry::getUser())) {
            return $user->getId();
        }
        // Logic to authenticate the user for the given request. If it fails...
        throw new UnauthorizedHttpException(null, 'The API key you provided was not correct.');
    }
}

use Dingo\Api\Routing\Controller;
use Dingo\Api\Dispatcher;
use Dingo\Api\Auth\Shield;

class UserApiController extends Controller
{
    /**
     * Create a new controller instance.
     *
     * @param  \Dingo\Api\Dispatcher  $api
     * @param  \Dingo\Api\Auth\Shield  $auth
     */
    public function __construct(Dispatcher $api, Shield $auth)
    {
        parent::__construct($api, $auth);

        if(($user = \Sentry::getUser())) {
            $this->auth->setUser($user);
        }

        $this->afterConstruct();
    }

    /**
     * @return \App\Model\User|null
     */
    public function getUser()
    {
        return $this->auth->user();
    }

    protected function afterConstruct()
    {

    }
} 

[philsturgeon]

Could you get something into PR form so I could play around with it?

[ryanhungate]

sure @philsturgeon, doing right now... update shortly

[philsturgeon]

Thanks! 

[ryanhungate]

hey @philsturgeon - https://github.com/ryanhungate/api
I have no clue if this will work for every aspect of the api package, but it seems to work... now when using a controller, and typing $this->api->user() - returns the Sentry user. Let me know if I fubared this thing :)

[jasonlewis]

We'll continue this discussion over on #60.