-
Notifications
You must be signed in to change notification settings - Fork 58
Can't work with Laravel Passport #61
Comments
This is quite interesting. I did some initial tweaking with this. I changed the (passport) migrations (published them) to use binary UUIDs everywhere. I extended all Passport models with my own. You can use
I applied the README parts about model modifications to the custom Passport models. I saw a working |
Hi @afraca
I did the same, you can have a look at the source code. But unfortunately, this is not enough, for example, for some cases Passport want to convert a token into a response, which requires using the The package I published has been tested for all the grant types, currently works fine for me. |
This package has been abandoned. Alternatives: https://github.com/michaeldyrynda/laravel-efficient-uuid & https://github.com/michaeldyrynda/laravel-model-uuid |
Laravel Passport will throw errors if using binary UUID.
I just created a package laravel-passport-binary-uuid-adapter to allow Passport accept binary UUID to work with this package.
I found some people encountering the same issue here, so if you don't mind, add a link to this package to your README will be helpful for people who are using Passport I think😃
The text was updated successfully, but these errors were encountered: