Status of UUID for client_id

[huntsfromshadow]

I know this has been talked about for a while,
but what is the current status of using UUID for client ID?

[fenos]

We are all waiting for this.

[JeanLucEsser]

Indeed we are.

[robonaparte]

Maybe @heisian can answer this.

[cweiske]

Duplicate of #14.

[heisian]

Sadly I'm in node world now since that's what my new occupation uses.. If I have some extra time I'll take a look at my passport fork and see what's changed - it's been a while. I wouldn't bank on my fork getting merged in anytime soon, though, unless Taylor sees overwhelming support for it. He was not a fan when I originally made a PR :P

[roblesterjr04]

Any more updates on this? It seems strange that this wasn't an original feature. Not a single API service in existence uses an incrementing Integer for a client ID.

[mosleim]

i'm waiting for this updates.

[diadal]

I create a simple package for this, it convert client id in all the table to Uuid.
https://github.com/diadal/passport

[mloberg]

You can use UUIDs by updating the migrations and using model listeners. https://mlo.io/blog/2018/08/17/laravel-passport-uuid/

[driesvints]

Gonna close this as it's a duplicate of #14

[baig772]

I create a simple package for this, it convert client id in all the table to Uuid.
https://github.com/diadal/passport

I am having issues installing this. Will this work with Laravel 5.7 ?

[Sephster]

Probably better to ask that question in the diadal/passport repo instead.