Passport: Using Config

[nueko]

Hi, just curious, is it bad idea if passport use config, and make it easy to us to adjust what our project needs?

[Frozire]

Which adjustments are you thinking?

Everything adjustable that doesn't break the OAauth2 standard is already adjustable through the Passport class. By extending Passports classes, or overriding specific routes, you can override most of the functionality.

Ex: I needed OAuth clients to be managed by my organization and not by individual users. Done simply by replacing the routes to the ClientController with methods for handling clients.

[nueko]

table name, for example

[nueko]

Controllers used also nice if they are configurable

[jaumesala]

Being really _"purist"_: The cookie name laravel_token.
Somehow, it exposes the OAuth "package" used in the Back-end... :stuck_out_tongue_winking_eye:

[robinvdvleuten]

It would also be the case if you want to override the domain of the laravel_token cookie domain which uses the session domain cookie by default.

[themsaid]

Closing for lack of activity, hope you got the help you needed :)