Skip to content

[11.x] Fix the multiple authorization providers in Laravel Passport #1656

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

michaelnabil230
Copy link
Contributor

@michaelnabil230 michaelnabil230 commented Apr 25, 2023

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 the admin 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 the user provider as well, the token will be created with the user provider.

This is achieved by adding a new provider field to the createToken method in the TokenFactory class, which allows specifying the provider for the token. Additionally, the AuthCode and RefreshToken models now have a provider 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.

@michaelnabil230 michaelnabil230 changed the title [11.x] Add support for multiple authorization providers in Laravel Passport [11.x] Fix the multiple authorization providers in Laravel Passport Apr 25, 2023
@taylorotwell
Copy link
Member

I honestly can't handle anymore Passport customization PRs right now. I need a break from it. Feel free to fork Passport to meet your needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants