You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Big surprise, it was me. For some reason (probably -- definitely -- me not understanding the implications of what I did) I had changed the 'defaults' guard in config/auth.php FROM web to api. Your documentation didn't suggest that. I can't tell you why I thought it was a good idea. No answer puts me in a good light, so I'll own it.
There is no bug. There's only a user proving once again that nothing is foolproof because fools are so ingenious.
However, changing the default guard like that shouldn't cause the issue you're seeing. I'll reopen this and see if I can recreate it because that definitely shouldn't be happening.
This is quite possibly me doing something wrong, but I can successfully set a token for a user and retrieve the user information via
$user =Auth::guard('api')->user()
(And there was much rejoicing.)as long as our old friend
\App\Http\Middleware\EncryptCookies::class
is not active in the 'api' middleware group. (less rejoicing occurs)
Put another way, it appears that the
api_login_
token is getting encrypted, but it's not getting decrypted. Is there something I'm missing?The text was updated successfully, but these errors were encountered: