Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When multiple guard users use the sanctum driver, there is a problem that session users are confused.
Example:
config/auth.php
config/sanctum.php
Now login admin guard user, and print all guard user
routes/api.php
result: api guard return admin user
For this we need to check the type of user or add middleware to fix the problem, but this is not a good idea.
New auth config like:
sanctum driver need to know which guard can be scanned, private, not global.
If there no with_guard field or with_guard is null, driver will use old rules.