{"action":"opened","issue":{"url":"https://api.github.com/repos/lucadegasperi/oauth2-server-laravel/issues/549","labels_url":"https://api.github.com/repos/lucadegasperi/oauth2-server-laravel/issues/549/labels{/name}","comments_url":"https://api.github.com/repos/lucadegasperi/oauth2-server-laravel/issues/549/comments","events_url":"https://api.github.com/repos/lucadegasperi/oauth2-server-laravel/issues/549/events","html_url":"https://github.com/lucadegasperi/oauth2-server-laravel/issues/549","id":106420153,"number":549,"title":"Authorizer::getResourceOwnerID() Globally for All Routes","user":{"login":"dtirer","id":639812,"avatar_url":"https://avatars.githubusercontent.com/u/639812?v=3","gravatar_id":"","url":"https://api.github.com/users/dtirer","html_url":"https://github.com/dtirer","followers_url":"https://api.github.com/users/dtirer/followers","following_url":"https://api.github.com/users/dtirer/following{/other_user}","gists_url":"https://api.github.com/users/dtirer/gists{/gist_id}","starred_url":"https://api.github.com/users/dtirer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dtirer/subscriptions","organizations_url":"https://api.github.com/users/dtirer/orgs","repos_url":"https://api.github.com/users/dtirer/repos","events_url":"https://api.github.com/users/dtirer/events{/privacy}","received_events_url":"https://api.github.com/users/dtirer/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-14T20:22:00Z","updated_at":"2015-09-14T20:22:00Z","closed_at":null,"body":"I'm using this package and am able to call `Authorizer::getResourceOwnerId()` to get the logged in User.  However, I would prefer to not call this on every Controller Method.\r\n\r\nMy question is, how would you integrate this functionality so that you could access $this->user (or similar) from every route without having to explicitly call `$user = User::find(Authorizer::getResourceOwnerId())` every time.\r\n\r\nOr this perhaps not the best way to go about accessing your logged in user?"}}