Add the ability to store the token in the database/redis

[dan-lutd]

Summary

On sites with filesystems like Heroku, the file storage of generated files flushed every restart and at least every 24 hours.
For images ie user profile pic, AWS or other is suggested.
But for authentication I'd like to use the database or redis if needed to scale.
Each user may have multiple devices and therefor multiple rows in the token table.
For example token_id, token (hashed) user_id, device_id, device_name, platform

We would like to present a list of devices to the user and let them choose to unauthorize them.

[eschricker]

In my opinion, this functionality does not need to be included in the library.

You ca create a database table that contains all your tokens with the different claims. To do this, you need to change your login an refresh methods. If you want to unauthorize specific token, you can blacklist them. The functionality to blacklist tokens is implemented in this library.

[leon0399]

The main cause for JWT is that it shouldn't be stored anywhere, but validated using cryptographic algorithms
Perhaps in your case you may look for other solutions

[Messhias]

I believe this issue should be not forwarded as peer @eschricker advised with @leon0399.

If you think should keep this request open feel free to open the issue again with more details and why should be added to the library.

[dan-lutd]

I understand if that is the direction the developers want to go..
My use case uses the stored token record for all tokens for a user,
allowing a different token per device.
A user may then get a list of the other devices that have tokens and revoke that token by deleting it.
By just using the token blacklist I cannot see the other devices the user may use.

[mfn]

I think what you're looking for might a more feature-full implementation like https://laravel.com/docs/8.x/sanctum

[dan-lutd]

Exactly what I settled on. thanks

[leon0399]

A user may then get a list of the other devices that have tokens and revoke that token by deleting it.

This feature will be possible after #71