Extend Illuminate\Foundation\Auth\User

[dustinleblanc]

I've found that I am having to handle Auth0 user data and my database models separately which isn't very convenient. Using Eloquent's User::firstOrNew() isn't possible using Auth0User, but if decide to extend my user object from the default Eloquent object, I lose access to the added Auth0 data, I'd love to have peanut butter and chocolate 😄

[joshcanhelp]

Thanks for the note here @dustinleblanc ... we have a section on our quickstart that addresses Auth0 login along with a database:

https://auth0.com/docs/quickstart/webapp/laravel#extra-custom-user-handling

Is that helpful or are you looking to do something else?

[dustinleblanc]

Hey @joshcanhelp ! That documentation was helpful during implementation, I've just run into a limitation running that setup. I can load my user from the database, and access all the data we define for the user in the database tables, or I can instead load the user using's Auth0's provided classes and get the Auth0 metadata for the user, but at the current time I can't really see how to load both sets of data on a single object. I'd like to have my user model extend the Auth0User class provided by the plugin, but if I do, I lose access to the Eloquent methods that let me load the user from the database (and I am sure some other things). It feels like this could work if the Auth0 user extended the eloquent user, or could be made to more easily. Thanks!

This isn't a deal breaker btw, more of an improvement. We currently have the app on Laravel 5.2 if that matters.

Thanks!

[joshcanhelp]

What, exactly, are you trying to do that you're unable to? Would it be possible to extend the Eloquent model to extract that user data, using the Auth0 class as an example?

I'm definitely open to a different implementation here, as long as it doesn't mean we break everything!

[joshcanhelp]

No activity, closing.

[vomitHatSteve]

I don't know if this ticket should be re-opened but two use-cases include issue #114 and integrating with bouncer (https://github.com/JosephSilber/bouncer)

Apologies if necroing this thread is incorrect etiquette.

[joshcanhelp]

@vomitHatSteve - "necroing" is my favorite word of the month now, thank you for that 😆

Happy to re-open this. We're working on a major in the 7.0.0 branch (not a lot there currently) and I'm guessing the changes required to get this working how it should will include some breakage.

I'm happy to take a first pass at this once we've got our SDK major released and working in the 7.0.0 branch here but open to PRs and suggestions in the meantime!

[saltukalakus]

Hi @joshcanhelp , @lbalmaceda just wanted to put a brief note here as well for the internal eng. issue. I was able to reproduce the issue using this repository. Let me know if I can with anything else.

[joshcanhelp]

@vomitHatSteve @saltukalakus - Would you be able to give the change-user-model branch a try and see if it works for you?

https://github.com/auth0/laravel-auth0/tree/change-user-model

[vomitHatSteve]

This branch doesn't appear to introduce new issues for me, but I'm still stymied by #158 unfortunately.

[rlewkowicz]

I'm running into issues as well and I'm not skilled enough yet to fully understand it. I believe its that the user provider is not extending the native model? So I can't do something like:

Auth::guard(app('VoyagerGuard'))->getProvider()->getModel();

Its making it difficult to use some of these open source packages

[joshcanhelp]

@rlewkowicz - Does this branch solve your issue?

https://github.com/auth0/laravel-auth0/tree/change-user-model

Requires PHP 7.1, FYI.

[joshcanhelp]

We took a different approach here based on feedback. Please see the draft PR below to see what we're proposing:

#165

That new trait can be added to the Eloquent User model which can be returned from a custom User repository. If anyone has feedback on this, we'd appreciate it!

[evansims]

Closing this ticket as it's quite stale at this point, but the next major of this Laravel plugin will include a refactored user model that will address this, based on the work in the PR Josh linked above