Store SP in Database

[juliardi]

Is it possible to store the list of Service Provider in the database and grab it from there whenever someone login/logout ?
Or is it a security issue?

[upwebdesign]

@juliardi I suppose you could store them in a database. There is a lot of sensitive information being stored in databases. I don't see why this would be any different. Whether or not your database is secure is up to you. You should be able to set the config to your liking using the config helper in Laravel.

[juliardi]

@upwebdesign Is this library currently support fetching SP list from database ?
If it is, how do I config it?
If it is not, are there any plan to implement that feature? I believe by storing the SP list in the database would make updating the list easier

[upwebdesign]

@juliardi please see the config section of the readme.

[juliardi]

The config section only stated that the SP list stored in the config file, so I conclude currently this library doesn't support fetching SP list from database, but storing the SP list itself in the database is something allowable but would need a modification to this library. Thank you for your answer @upwebdesign.

[upwebdesign]

@juliardi yes, you are correct. This package does not support DB storage for SP's. This could possibly be a feature request.

[jrgilman]

@upwebdesign we are actually in the process of doing this for a piece of software we're working on and are curious if you're open to merging a PR from us for the feature.

We're debating about whether or not we want to do this by providing a ServiceProvider eloquent model in the package itself - or providing an abstract class and allowing the user to provide their own implementation as a config variable. If you have a preference let me know as that will effect which way we want to go with this - we would like to get this PR'ed into the package rather than maintaining our own "hard fork" of this package.

We would also make sure to provide a test suite that ensures it doesn't break any existing features that it touches.

[upwebdesign]

@jrgilman, involving the database with this package would expose a potential breaking change. If a database is considered, all SP information should be able to be stored in the database while still allowing for .env/config implementation. If your team would like to tackle a DB approach, that would be cool.