Closed EngHell closed 3 years ago
I've digging more inside of AttempToAuthenticate.php
protected function handleUsingCustomCallback($request, $next)
{
$user = call_user_func(Fortify::$authenticateUsingCallback, $request);
dd($user);
if (! $user) {
$this->fireFailedEvent($request);
return $this->throwFailedAuthenticationException($request);
}
$this->guard->login($user, $request->filled('remember'));
return $next($request);
}
$user
is null only after running any delete statement.
Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:
However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.
So i have created a custom controller to hangle the "/login" post route, which is exactly as the one provided in the src but with a modified Request injection for renaming password to token.
The issue arises in this code(JetstreamServiceProvider.php):
As you can see i have commented some code sections as i have been experimenting, even retrieving the user after the token delete with
User::where("email",$request->email)
and even checking withdd
says$user
is not null in all cases but even then the response in the default jetstream view isBut removing any delete query makes it work as intended.
Whats supposed to happen:
What happens: At step 4 the log in fails even with the return not being null or false.