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
I've got an app that uses multiple guards. On routes without any auth middleware on blade's @can will use the default guard. This means that the policies don't always work the way I'd like - if a user is logged in via a different guard.
Currently what I've decided to do is this in my auth service provider:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I've got an app that uses multiple guards. On routes without any auth middleware on blade's
@can
will use the default guard. This means that the policies don't always work the way I'd like - if a user is logged in via a different guard.Currently what I've decided to do is this in my auth service provider:
Is there a better way to accomplish this? Or a way to set the user resolver only for blade?
Beta Was this translation helpful? Give feedback.
All reactions