[11.x] Fix the multiple authorization providers in Laravel Passport #1656
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.
This PR adds support for multiple authorization providers in Laravel Passport. Currently, when a user logs in with the
admin
provider, the token is created with theadmin
provider as well, even if the user has access to other providers.With this PR, users can now log in with any provider they have access to, and the token will be created with the corresponding provider. For example, if a user login with the
admin
provider but has access to theuser
provider as well, the token will be created with theuser
provider.This is achieved by adding a new
provider
field to thecreateToken
method in theTokenFactory
class, which allows specifying the provider for the token. Additionally, theAuthCode
andRefreshToken
models now have aprovider
field to store the provider associated with the token.Overall, this PR improves the flexibility and usability of Laravel Passport for applications with multiple authorization providers.
It complements the idea of (#1655)
I think we need to display an error exception if the auth provider is not available in the config file.