Is there any other way to store session-related information in a database to make refresh tokens thread-proof in Golang?
If you don't want your users' refresh tokens to get invalid when restarting your server, there has to be token storage (in-memory, or remote dbs) that stores that info for them.
If you don't want your users' refresh tokens to get invalid when restarting your server, there has to be token storage (in-memory, or remote dbs) that stores that info for them.
December 1, 2024 at 6:55 PM
Is there any other way to store session-related information in a database to make refresh tokens thread-proof in Golang?
If you don't want your users' refresh tokens to get invalid when restarting your server, there has to be token storage (in-memory, or remote dbs) that stores that info for them.
If you don't want your users' refresh tokens to get invalid when restarting your server, there has to be token storage (in-memory, or remote dbs) that stores that info for them.
A calm setup to work on for hours 🧘🏽
November 26, 2024 at 2:15 PM
A calm setup to work on for hours 🧘🏽