Auth not initialized when route is registered within service provider boot method
0
Why is Auth not being initialized when the route is registered within service provider boot method?
SCENARIO 1: Auth is Okay
web.php
Route::get("/user", "UserController@index");
User Controller Class:
Class UserController extends Controller
function index()
if(Auth::check()) // returns true
// perform action
else
// redirect here
SCENARIO 2: Auth is not initialized
But when you register the route inside boot of a ServiceProvider Auth::check now is returning false. It seems the Auth properly initialized when called this way.
...
AppProvidersRouteServiceProvider::class,
/*
* UserServiceProvider
*/
AppProvidersUserServiceProvider::class,
],
...
User Service Provider Class:
class UserServiceProvider extends ServiceProvider
public function boot()
Route::get("/user", "UserController@index");
User Controller Class:
Class UserController extends Controller
function index()
if(Auth::check()) // returns false
// perform action
else
// redirect here
laravel laravel-5.7
asked Nov 14 '18 at 7:12
jdcjdc
4518
add a comment |
0
Why is Auth not being initialized when the route is registered within service provider boot method?
SCENARIO 1: Auth is Okay
web.php
Route::get("/user", "UserController@index");
User Controller Class:
Class UserController extends Controller
function index()
if(Auth::check()) // returns true
// perform action
else
// redirect here
SCENARIO 2: Auth is not initialized
But when you register the route inside boot of a ServiceProvider Auth::check now is returning false. It seems the Auth properly initialized when called this way.
...
AppProvidersRouteServiceProvider::class,
/*
* UserServiceProvider
*/
AppProvidersUserServiceProvider::class,
],
...
User Service Provider Class:
class UserServiceProvider extends ServiceProvider
public function boot()
Route::get("/user", "UserController@index");
User Controller Class:
Class UserController extends Controller
function index()
if(Auth::check()) // returns false
// perform action
else
// redirect here
laravel laravel-5.7
asked Nov 14 '18 at 7:12
jdcjdc
4518
It hasn't being initialized yet because the purpose of the providers is to initialize things
– cbaconnier
Nov 14 '18 at 7:21
accounting to Laravel Documentation - Service Provider - In general, we mean registering things, including registering service container bindings, event listeners, middleware, and even routes. Service providers are the central place to configure your application.
– jdc
Nov 14 '18 at 8:08
If this is the case, why register route inside service provider then?
– jdc
Nov 14 '18 at 8:09
"Service providers are responsible for bootstrapping all of the framework's various components, such as the database, queue, validation, and routing components. " laravel.com/docs/5.7/lifecycle
– cbaconnier
Nov 14 '18 at 8:14
You can define route in ServiceProvider within theregistermethod like said in the Service Provider Documentation. Normaly It's supposed to work, due to the fact that every thing which have been define in every register Service Provider will already been define and ready to work
– Yves Kipondo
Nov 19 '18 at 15:24
add a comment |
0
0
0
Why is Auth not being initialized when the route is registered within service provider boot method?
SCENARIO 1: Auth is Okay
web.php
Route::get("/user", "UserController@index");
User Controller Class:
Class UserController extends Controller
function index()
if(Auth::check()) // returns true
// perform action
else
// redirect here
SCENARIO 2: Auth is not initialized
But when you register the route inside boot of a ServiceProvider Auth::check now is returning false. It seems the Auth properly initialized when called this way.
...
AppProvidersRouteServiceProvider::class,
/*
* UserServiceProvider
*/
AppProvidersUserServiceProvider::class,
],
...
User Service Provider Class:
class UserServiceProvider extends ServiceProvider
public function boot()
Route::get("/user", "UserController@index");
User Controller Class:
Class UserController extends Controller
function index()
if(Auth::check()) // returns false
// perform action
else
// redirect here
laravel laravel-5.7
asked Nov 14 '18 at 7:12
jdcjdc
4518
Why is Auth not being initialized when the route is registered within service provider boot method?
SCENARIO 1: Auth is Okay
web.php
Route::get("/user", "UserController@index");
User Controller Class:
Class UserController extends Controller
function index()
if(Auth::check()) // returns true
// perform action
else
// redirect here
SCENARIO 2: Auth is not initialized
But when you register the route inside boot of a ServiceProvider Auth::check now is returning false. It seems the Auth properly initialized when called this way.
...
AppProvidersRouteServiceProvider::class,
/*
* UserServiceProvider
*/
AppProvidersUserServiceProvider::class,
],
...
User Service Provider Class:
class UserServiceProvider extends ServiceProvider
public function boot()
Route::get("/user", "UserController@index");
User Controller Class:
Class UserController extends Controller
function index()
if(Auth::check()) // returns false
// perform action
else
// redirect here
laravel laravel-5.7
laravel laravel-5.7
asked Nov 14 '18 at 7:12
jdcjdc
4518
asked Nov 14 '18 at 7:12
jdcjdc
4518
asked Nov 14 '18 at 7:12
jdcjdc
4518
asked Nov 14 '18 at 7:12
jdcjdc
4518
asked Nov 14 '18 at 7:12
jdcjdc
4518
4518
It hasn't being initialized yet because the purpose of the providers is to initialize things
– cbaconnier
Nov 14 '18 at 7:21
accounting to Laravel Documentation - Service Provider - In general, we mean registering things, including registering service container bindings, event listeners, middleware, and even routes. Service providers are the central place to configure your application.
– jdc
Nov 14 '18 at 8:08
If this is the case, why register route inside service provider then?
– jdc
Nov 14 '18 at 8:09
"Service providers are responsible for bootstrapping all of the framework's various components, such as the database, queue, validation, and routing components. " laravel.com/docs/5.7/lifecycle
– cbaconnier
Nov 14 '18 at 8:14
You can define route in ServiceProvider within theregistermethod like said in the Service Provider Documentation. Normaly It's supposed to work, due to the fact that every thing which have been define in every register Service Provider will already been define and ready to work
– Yves Kipondo
Nov 19 '18 at 15:24
add a comment |
It hasn't being initialized yet because the purpose of the providers is to initialize things
– cbaconnier
Nov 14 '18 at 7:21
accounting to Laravel Documentation - Service Provider - In general, we mean registering things, including registering service container bindings, event listeners, middleware, and even routes. Service providers are the central place to configure your application.
– jdc
Nov 14 '18 at 8:08
If this is the case, why register route inside service provider then?
– jdc
Nov 14 '18 at 8:09
"Service providers are responsible for bootstrapping all of the framework's various components, such as the database, queue, validation, and routing components. " laravel.com/docs/5.7/lifecycle
– cbaconnier
Nov 14 '18 at 8:14
You can define route in ServiceProvider within theregistermethod like said in the Service Provider Documentation. Normaly It's supposed to work, due to the fact that every thing which have been define in every register Service Provider will already been define and ready to work
– Yves Kipondo
Nov 19 '18 at 15:24
It hasn't being initialized yet because the purpose of the providers is to initialize things
– cbaconnier
Nov 14 '18 at 7:21
It hasn't being initialized yet because the purpose of the providers is to initialize things
– cbaconnier
Nov 14 '18 at 7:21
accounting to Laravel Documentation - Service Provider - In general, we mean registering things, including registering service container bindings, event listeners, middleware, and even routes. Service providers are the central place to configure your application.
– jdc
Nov 14 '18 at 8:08
accounting to Laravel Documentation - Service Provider - In general, we mean registering things, including registering service container bindings, event listeners, middleware, and even routes. Service providers are the central place to configure your application.
– jdc
Nov 14 '18 at 8:08
If this is the case, why register route inside service provider then?
– jdc
Nov 14 '18 at 8:09
If this is the case, why register route inside service provider then?
– jdc
Nov 14 '18 at 8:09
"Service providers are responsible for bootstrapping all of the framework's various components, such as the database, queue, validation, and routing components. " laravel.com/docs/5.7/lifecycle
– cbaconnier
Nov 14 '18 at 8:14
"Service providers are responsible for bootstrapping all of the framework's various components, such as the database, queue, validation, and routing components. " laravel.com/docs/5.7/lifecycle
– cbaconnier
Nov 14 '18 at 8:14
You can define route in ServiceProvider within the
register method like said in the Service Provider Documentation. Normaly It's supposed to work, due to the fact that every thing which have been define in every register Service Provider will already been define and ready to work– Yves Kipondo
Nov 19 '18 at 15:24
You can define route in ServiceProvider within the
register method like said in the Service Provider Documentation. Normaly It's supposed to work, due to the fact that every thing which have been define in every register Service Provider will already been define and ready to work– Yves Kipondo
Nov 19 '18 at 15:24
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53294853%2fauth-not-initialized-when-route-is-registered-within-service-provider-boot-metho%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53294853%2fauth-not-initialized-when-route-is-registered-within-service-provider-boot-metho%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It hasn't being initialized yet because the purpose of the providers is to initialize things
– cbaconnier
Nov 14 '18 at 7:21
accounting to Laravel Documentation - Service Provider - In general, we mean registering things, including registering service container bindings, event listeners, middleware, and even routes. Service providers are the central place to configure your application.
– jdc
Nov 14 '18 at 8:08
If this is the case, why register route inside service provider then?
– jdc
Nov 14 '18 at 8:09
"Service providers are responsible for bootstrapping all of the framework's various components, such as the database, queue, validation, and routing components. " laravel.com/docs/5.7/lifecycle
– cbaconnier
Nov 14 '18 at 8:14
You can define route in ServiceProvider within the
registermethod like said in the Service Provider Documentation. Normaly It's supposed to work, due to the fact that every thing which have been define in every register Service Provider will already been define and ready to work– Yves Kipondo
Nov 19 '18 at 15:24