Update May 6th, 2020: Laravel has released Passport 9.0, which supports UUIDs out of the box!
Knives over Forks
There have been solutions such as forking Passport and changing to a UUID. I would recommend not taking this approach because forks have a history of becoming unmaintained.
Luckily, we can make this change without modifying any of Passport’s code. Using model listeners, we can hook into the client’s life cycle and make the changes we need.
First we need to modify the migrations that Passport provides to make the changes at the database level. This is done by adding
AppServiceProvider@register and then publishing the migrations with
php artisan vendor:publish --tag=passport-migrations. Once we have the migrations published, we need to edit any
client_id field to be a uuid type.
Now that we’ve made our changes to the database, we need to generate UUIDs when a client is created. This can be done by using the
::creating model event listener. Let’s add this to our
I’m using the Ramsey UUID package, but you could use any other package or method for generating a UUID. You’ll also notice that incrementing is set to
false. By default, Eloquent will cast id fields to integers, so you may end up seeing this output if you don’t add that line:
Personal access client created successfully. Client ID: 0 Client Secret: ZHywkvb0EPg0fYcxbdAlYLWhVSK0IHjoy5dW1j3B Password grant client created successfully. Client ID: 0 Client Secret: NykgD7a94EBCnz0owASEaFz8tQKo6T7KBJGOX2YU
We’ve got our clients saving an auto-generated UUID, but what about when fetching a client? The ID will still be cast to an integer. Using model event listeners again, we can have it not cast to an integer. Add this to your
That was easy
With just a few lines of code, none of which overwrites base Passport code, we’ve got UUID client IDs instead of auto-incrementing IDs.
Comments? I'm @mloberg on Twitter.